-
Notifications
You must be signed in to change notification settings - Fork 1
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
Do we actually want to use Dialog for the Mean Info? #230
Comments
Design team wants this to be a non-modal dialog! Or at least a non-modal viewable thing. Questions:
@zepumph will take it from here. |
I created phetsims/sun#882 and will report back with a recommendation on how to proceed in this sim. |
Today during Dev meeting, it was recommended that we just use a non |
This is ready for review by @jbphet. |
Nice. Changes look good, and it seems like a significant improvement. Closing. |
While working on a comment from #196, I discovered that 1 year ago Marla had implemented the Dialog API incorrectly. This is why we can see strange things in the studio tree where the dialog has both a
visibleProperty
andisShowingProperty
:It is not an expected part of Dialog's API to use a
visibleProperty
to toggle on and off the appearance of the dialog.This incorrect implementation allowed us to do things that are not normally part of dialog UX. For example normally when a dialog pops up in our sims, the background darkens, and as soon as you click anywhere outside of the dialog the dialog immediately goes away.
Dialog Implementation:
Current Implementation:
This discovery is unfortunate because @amanda-phet pointed out that during interviews a student was exploring moving the balls around while seeing the calculations change in real time.
In the end this is a design decision. We can keep the current behavior we have, and I move away from using a Dialog and instead it will act as a Node that is in front of everything in the notepad, or we use the Dialog API as is intended, and lose some of the current behavior, but remain more consistent with PhET dialog UX.
This should be discussed synchronously to avoid confusion.
The text was updated successfully, but these errors were encountered: