🐞 Fix bug where frontmost application receives key events#631
Merged
mrkai77 merged 1 commit intoDec 14, 2024
Merged
Conversation
…y result in a discrepancy and transmit keyboard events to the front most application. - Keep track of the last key event and use that as a fallback if multiple keys have been inserted into `pressedKeys`.
mrkai77
approved these changes
Dec 14, 2024
Owner
mrkai77
left a comment
There was a problem hiding this comment.
Works like a charm, thank you so much! Also, I didn't know about how it was possible to put in #line inside print statements, love it!
This file contains hidden or 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.
This fix addresses the issue where pressing multiple keys quickly can cause a discrepancy and send keyboard events to the frontmost application.
I added a new instance variable called
lastKeybecausepressedKeysis aSetwhich is not ordered.Using the new instance variable as a fallback has fixed the issue for me.