-
Notifications
You must be signed in to change notification settings - Fork 13
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
How to instrument vectorVisibilityProperties #224
Comments
While we are at it over here, we should discuss the name too, from this comment in #219:
I personally think that these Properties are in fact controlling the visibility of items, and items that aren't instrumented, and so don't have their own |
@zepumph thanks for the explanation! I can see how the |
This issue should be reviewed at the next time Projectile Motion is worked on. |
Alright, classes and tandems have been renamed to
Anything else here @arouinfar? |
Looks good, thanks! |
From #219, @arouinfar had the review comment like:
I see. I also see
graphingQuadratics.exploreScreen.view.viewProperties
, which makes me feel like it is a bit better to just go with how the sim has implemented these. I can see them fitting in either, if there is a strong preference, then we can probably refactor, but to be honest I would prefer to see them in the view. They have nothing to do with the projectiles' model, and instead only with how information is displayed (hence the view). This is not to say that the GAO instrumentation is incorrect, but perhaps the decision in GAO would be different if there were multiple (4 in PM and 7 in GQ).What do you think @arouinfar @kathy-phet?
The text was updated successfully, but these errors were encountered: