-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert simulations to use EnabledProperty #340
Comments
I feel like this is not really necessary. I don't feel like it is buying us enough to warrant going back to convert old usages. A great time to do this would be when outfitting a sim with PhET-iO, since having a consistent phet-io API for Part of my recommendation is not believing that |
Thanks for your comments. I'm inclined to add a step to the instrumentation guide to consider this, but one distinction is that |
bringing to phet-io meeting to move this along. |
This type does three things:
Designers during today's meeting felt like the above was appropriate. We can convert simulations now. Likely we will do this lazily. @samreid can you update the code review documentation to mention that this should be used when appropriate? |
I added a code review checklist item about using EnabledProperty. I also decided to add an "opt-out" option for the strict name check--that seemed better than writing that in an issue or checklist. @zepumph can you please review? It should be quick. |
In phetsims/scenery#1100 @zepumph introduced
EnabledProperty
and it is working nicely. There are 16 occurrences ofenabledProperty = new BooleanProperty
and another 9 occurrences ofenabledProperty = new Property
. For instance:Masses and Springs:
Should many or all of these be converted to use
EnabledProperty
instead? If so, should this be a chip-away for responsible-devs, or something @zepumph or I should do?The text was updated successfully, but these errors were encountered: