🐛 Add hotkey reset logic to avoid stuck keys #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Occasionally, the hotkey management logic would get "stuck" thinking a key is pressed when it isn't.
This can happen if keyboard events are prevented from reaching the FlashCom process for a variety of reasons (ex. if the user invokes the lock screen with Win+L, the key-up event for the Win key will not reach FlashCom).
This change adds a hotkey reset timer that resets all hotkey state after 1 second of inactivity. The timer is reset each time a new hotkey key is pressed. This will prevent FlashCom from maintaining a bad keyboard state, even if keyboard events are interrupted.
This change also bumps the version to 0.2.1.