-
Notifications
You must be signed in to change notification settings - Fork 7
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
Should environmentNode.visibleProperty be read-only? #263
Comments
If for some reason we need to support hiding the environmentNode and everything that's on top of it (clock, radio buttons, push buttons) then we will need to add an additional parent element for all of those things, Studio tree is currently: It would change to:
|
Yikes! I don't know how we didn't notice this before when we reviewed studio. Let's definitely make this read-only. I can't think of a reason to want to set |
@amanda-phet what do you think about the restructuring of the Studio tree that I proposed in #263 (comment)? Of is just making |
I prefer to not restructure the tree that way. I also think it would be incredibly strange for someone to want to hide the entire environment (or |
OK, no I have made |
Re the tree structure... @amanda-phet and I discussed this more on Slack. We discussed how this part of the UI might be interpretted by the instructional designer: Is it a panel with the clock, radio buttons, and push buttons on top of it? (siblings in the tree, the current implementation) Or is it a panel, with the clock, radio buttons, and push buttons inside of it? (children of the panel in the tree) We decided that the latter made more sense, and that's the structural change that I describe in #263 (comment). This is a relatively easy change, and is nice structural improvement, so I will make it so. And |
@amanda-phet ready for review. The revised tree structure is shown below. And these 2 elements are now read-only:
|
Looks great! Glad we made the change. |
I noticed that
*.environmentNode.visibleProperty
is not currently read-only. When it's set to false, it looks odd, see screenshot below. Should it be read-only?The text was updated successfully, but these errors were encountered: