-
Notifications
You must be signed in to change notification settings - Fork 18
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
debounser for inputs? #60
Comments
That's interesting, what is the advantage of a global heartbeat over say implementing a throttle on the widget itself? |
When I tested in the DSP platform I was on, a global heartbeat added the extra help:
|
BTW, a popular 'global heartbeat' is |
That is pretty close to what we have at the moment. The draw is only triggered when there is data changes and so there are no unnecessary frames. |
oops |
That could help when the input box or other GUI-data element is active, to help delay results until final input is entered. Typing you want to wait, unless it is an auto-populating dropbox, & you would still wait for a few characters/0.5 seconds Knobs I got away with 15FPS. |
Testing:
99
9
key is pressed, the value entered is09
, & the sliders jump to the left9
, the intended value of99
is fully entered, & sliders jump to rightThough here only 2 sliders are affected, but imagine a large spreadsheet that graphs results? That could be alot of jumpiness in the SPA.
In another platform, we would prevent jumpy values (& reduce CPU usage) by having a global 'heartbeat' function. Please let me know if you want a demo/explanation (bit long to explain).
The text was updated successfully, but these errors were encountered: