search

phetsims / area-builder

"Area Builder" is an educational simulation in HTML5, by PhET Interactive Simulations.
http://phet.colorado.edu/en/simulation/area-builder
GNU General Public License v3.0
1 stars 2 forks source link

Game: clicking eraser button doesn't make "Try Again" button disappear #80

Closed pixelzoom closed 8 years ago

pixelzoom commented 9 years ago

As noted in screenshot_584...

Interacting with specific things in the Game makes the "Try Again" button disappear. And it seems to be limited to things that change the user's "answer" in some way. For example, in Level 1 (screenshot) below, moving any blue square makes the "Try Again" button disappear, but toggling check boxes does not.

If this is indeed the desired behavior, then the eraser button seems to be buggy. It changes the user's answer, but the "Try Again" button does not disappear.

There may be other things like this in other types of challenges. I've only noted this one example.

screenshot_584

pixelzoom commented 9 years ago

I looked through all 6 game levels, and the eraser button appear to be the only problem.

pixelzoom commented 9 years ago

Discussed with @jbphet.

For the challenges that have a calculator (levels 3 & 4?), the user's answer is what's been entered into the calculator, and the boxes you can drag around are aids to help you think about the area. So I think it's appropriate that the eraser button doesn't make the "Try Again" button disappear, because it's not changing the user's answer.

But in the challenges where the user's answer is the number of boxes they've dragged in (levels 1, 2, 5 & 6?), pressing the eraser button does change the user's answer. The "Try Again" button should therefore disappear and be replaced with a (disabled) "Check" button.

amanda-phet commented 9 years ago

I agree with the above comment.

But in the challenges where the user's answer is the number of boxes they've dragged in (levels 1, 2, 5 & 6?), pressing the eraser button does change the user's answer. The "Try Again" button should therefore disappear and be replaced with a (disabled) "Check" button.

If it is significantly easier to implement this behavior for all levels (including 3-4 which are keypad challenges) then I don't think we should work too hard around this specification.

jbphet commented 8 years ago

Should now be fixed, I'll have the QA team verify on the next release candidate.

phet-steele commented 8 years ago

Looks fixed in 1.1.0-rc.1.