-
Notifications
You must be signed in to change notification settings - Fork 6
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
projectorModeCheckbox PhET-iO tree structure #654
Comments
This is now the new structure. Notice that it isn't blue, because it isn't linked, but we also don't have an extra @samreid please review the commits. @arouinfar please review if this is an alright cleanup change for the studio tree structure, and let me know if you think this should be added to SOM. if you do think it should be added. This can not and should not be included in a later MR, since it breaks the API, thus it would have to be added for the release tomorrow, or never added. Marking high priority in case you want to squeeze it in (I doubt that is what we want to do). |
@zepumph the tree structure looks good to me. @kathy-phet @jbphet and I discussed this a bit in phetsims/states-of-matter#346, and we decided it wasn't critical for the 1.2.0 release. Since it can't be included in a MR, I'm fine with leaving it out. Clients should be using the query parameter for projector mode, anyway. |
This looks like the optimal implementation to address these issues, nice work! I'm also glad we tried out the strategy to make API calls to linked elements work the same as calls to core elements. I don't have any recommendations for the review. I don't mind that it won't be in States of Matter 1.2.0, it will go out with other PhET-iO simulations published after today. @zepumph can this be closed? |
I see that Otherwise I am ready to close. |
Over in phetsims/states-of-matter#346, @jbphet and I realized it was weird that there was a linked property right next to the checkbox. I think it would be best to not link there, and instead just have the passed in property be called "property" I will take a look.
Here is what the structure looks like:
The text was updated successfully, but these errors were encountered: