Fire control clicks immediately and start looping after a short delay #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
When clicking a control button too quickly (as in, mouse isn't held down longer than 100 ms) the click doesn't register at all. A better user experience would be that any click, no matter how long pressed down, would register at least once.
Another good user experience is to start repeating clicks (due to holding down the control button) only after a brief delay. This is so that minute change can be made with single clicks without the risk of accidentally triggering the fast loops (100ms cycles).
Closes #27
Changes
controlClick()
outside of thesetInterval()
body. This will trigger a call immediately when clicking a control button.setInterval()
loop in asetTimeout()
to delay the loop by half a second (in line with other Windows user experiences, such as holding down a key on your keyboard).