Closed arouinfar closed 7 years ago
@arouinfar this was intentional.
@samreid basically did this at the time because he thought it looked cool and the team agreed (it was sort of a bell and whistle at the time). However, I don't think the idea of interfering with predictive questions was considered.
It seems a static image has become more of our standard, so I think it would be fine to make it static. I would say for acceleration use an image that shows some level of acceleration present on the meter. I think the speedometer is iconic enough that it does not matter whether the speed in the icon is zero or some nominal speed.
@arouinfar I agree certainly seems like an easy tweak to make for the next deploy/maintenance release.
Thanks @ariel-phet!
he thought it looked cool and the team agreed
My initial reaction was along the lines of "wow, that's cool!" so I can see how the behavior made it into the sim. :)
I would say for acceleration use an image that shows some level of acceleration present on the meter.
I think ~5 m/s^2 looks pretty good
I think the speedometer is iconic enough that it does not matter whether the speed in the icon is zero or some nominal speed.
Agreed. For consistency with ESPB, I would leave the needle at zero.
@arouinfar @ariel-phet here is the latest with this change:
Are we ready to redeploy this maintenance release?
Looks good! I think everything's ready for the redeploy @jessegreenberg, but @ariel-phet can confirm.
Thanks @arouinfar, I think we are ready to go. Closing this issue and I will track the maintenance release in #217.
While reviewing #217, I noticed that the speed and acceleration meter icons next to the checkboxes dynamically update. This behavior differs from ESPB, where the speedometer icon is a static image.
At rest:
While in motion:
@jessegreenberg has confirmed that this behavior dates back to FAMB 1.0.0. Frankly, I find it a bit odd, and I think that it has the potential to interfere with predictive questions.
@ariel-phet do you remember a discussion about this particular behavior? Was it intentional? If not, is this something we can/should address in the upcoming redeploy?