Needle points to incorrect values when setValues are done is quick succession.

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Go to http://jsfiddle.net/eBfTs/
2. Hit 'run'
3. Wait ten seconds

What is the expected output? What do you see instead?

I expect the needle to *start* to move towards each of the new values a few 
milliseconds after setValue is called.

Instead I see the needle 'bouncing' up and down, and taking several seconds to 
settle on 200.  In Chrome it is going 50->150->50->200.

What version of the product are you using? On what operating system?

jsgauge v0.4.2  Windows XP and Ubuntu.

Please provide any additional information below.

My application occasionally receives several update in a second.  On several 
occasions I have seen the needle get 'stuck' pointing at a number, which is 
different from the displayed value, for several seconds.  (i.e. the needle 
points at 50 for a few seconds, while the number displays 200).  I have not 
been able to replicate this behaviour in the fiddle - it is probably triggered 
by having a moderately busy page (two gauges and three flot graphs). 

Is there a *safe* maximum rate at which setValue can be called (either per 
gauge, or per all gauges)?

Original issue reported on code.google.com by cms...@gmail.com on 14 Dec 2011 at 11:19

[GoogleCodeExporter]

This issue was closed by revision r62.

Original comment by dragos.tihauan on 14 Dec 2011 at 8:56

• Changed state: Fixed

[GoogleCodeExporter]

Thanks, I'll try this shortly.

Original comment by cms...@gmail.com on 15 Dec 2011 at 9:22