-
Notifications
You must be signed in to change notification settings - Fork 2
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
Review instrumentation of colorProfile
#261
Comments
Here is the full list of the instrumented colors. All 3 density-buoyancy-common sims are the same, even though these colors don't necessarily appear in all sims. In general, these colors correspond to the fluids in the pool and the materials inside the bottle, which seem like useful things to let clients control. I'd like to wait for #265 to wrap up before working on this issue. |
We discussed this in today's design meeting over in #268 (comment). I'll leave this on hold until #268 is completed. |
#268 Is almost done, and no longer holding this one. |
Density does not require any instrumentation of the color profile, as the Mystery blocks all have a Buoyancy and Buoyancy: Basics both have the same set of instrumented colors: None of these colors need to be customizable, so I recommend uninstrumenting them. In #268 (comment), we noted that customizing fluid colors, in particular, could be problematic. It would be nice to customize the colors of the mystery materials (T-Y) that don't have a textured appearance. Can we instrument those colors? To summarize:
|
In the commits, I uninstrumented all ColorProperties, then added read/write instrumentation for the mysteries T-Y. In studio I was able to customize the color, and I saw it was preserved in Test. Please review. |
Looks good on main, thanks @samreid! Closing. |
In phetsims/buoyancy#51 (comment) the devs asked:
The relevant paper trail is in #65 and it appears that the instrumented ColorProperties may be required for State.
I'd like to review
global.view.colors
for all sims in the suite and decide:phetioReadOnly: false
?The text was updated successfully, but these errors were encountered: