Comment 2 for bug 1538200
Revision history for this message
| Craig (craigeastonuk) wrote Re: Repeated calls to engine.SetValue() in the same JS "call-back" are not handled properly. | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Ahh I see!
This probably explains why I had some problems when I tried the timer work-around. Sometimes the re-sync just didn't seem to work. I experimented with different timer-settings and 50 seems to be OK most of the time, (but it still fails occasionally). Any longer and I was concerned that I might create my own race condition with two button presses in quick succession, (although thinking a bit more about this now, I suspect that the user wouldn't notice any ill effects from this so perhaps I should just increase the timer to something like 100 on the basis that 1/10th of a second for a slip "re-sync" delay when you release a button *probably* wouldn't be noticed.)
I agree that the most sensible option to fix this now would probably be to add a dedicated control for this "slip re-sync" function.
Thanks for the info.