-
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
On the first screen, you cannot unselect "×100" #109
Comments
That sure seems buggy to me. The Flash version has radio buttons for '1 ball' and 'continuous', changing the selection from 'continuos' to '1 ball' stops the flow of balls, and you have to press 'Start' to resume. The HTML5 version has 'x 1', 'x 10' and 'x All', and I would expect similar behavior -- the flow of balls should stop whenever the radio button changes, and you have to push "Play" to start the flow. Assigning to @amanda-phet since she's the designated designer. |
I should note this problem is observed in master and in the version published on the website, which is 1.1.3 |
"x All" is supposed to indicate that you are dropping ALL 100 balls. I could see changing this to a pause button when that happens, so you have the option to pause what is happening. I would also be fine with this stopping when you change radio buttons, but would this also change the interaction if "x 10" is selected? If you press play and change your mind, can you also abort the (10-n) remaining balls from falling? |
I don't think there's any question about that. The question is what happens if they change the selection to something else before all 100 balls have dropped. Either the radio buttons should be disabled until all 100 balls are dropped (which I'm not recommending) or "drop all 100 balls" should be stopped when the radio button select is changed (which I'm recommending). The Flash version stops the 'continuous' flow of balls if the radio button selection is changed. And yes, '×10' and '×All' would behave the same. If you change the selection, the action associated with your previous selection should stop. |
That interaction pattern seems logical to me. I'm happy with that change. |
OK, I will proceed with what I proposed. |
Do you want an immediate maintenance release for this issue? It will require an addition 30-60 minutes. Or do you want to wait until the next time the sim is published from master? There is currently no timeframe for publishing from master, and it will require a full QA cycle. |
Signed-off-by: Chris Malley <[email protected]>
Discussed with @amanda-phet. This sim has had some a11y work and will probably be published out of master for that. So no maintenance release, wait until published out of master for a11y. |
On Slack, @amanda-phet indicated that she wanted to discuss how this fix should be published with @ariel-phet. So assigning to @amanda-phet. |
Note that 'x All' was changed to 'x 100' in #110. |
Signed-off-by: Chris Malley <[email protected]>
…been released from the hopper, #109 Signed-off-by: Chris Malley <[email protected]>
This has been addressed in master, @amanda-phet please verify. When the radio button selection is changed, any balls that have not yet been released from the hopper are canceled, and the enabled state of the "Play" button is adjusted accordingly. |
@amanda-phet you could also verify this in 1.2.0-dev.4. |
Looks like it's working as expected. |
Once you have pressed "x All" and "Play", there is no way to stop it (aside from a reset). You can even change the radio button values to "x 10" and "x 1" but they keep coming. Is this the desired behavior?
Discovered in phetsims/sun#360
Assigned to @pixelzoom since he is listed as the responsible dev, and I'm not sure who the design team is.
The text was updated successfully, but these errors were encountered: