fix: Wayland pynput v1.7.7 workaround #106
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
XWayland/Wayland does not reliably allow for capture of single key strokes via keyboard event listener(s), but playing about showed key-combos are _mostly_ caught quickly! Also it seems on Arch Linux (I use Arch BTW™) the `key` object sent through the `keyboard.listener` has a different _shape_, or perhaps the inconsistencies in capture behaviors got me jumping to wrong-thinking. Either way, these proposed changes _should_ preserve previously programmed `key.char` detection, while also allowing those stuck with Wayland to enjoy this tool.
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.
XWayland/Wayland does not reliably allow for capture of single key strokes via keyboard event listener(s), but playing about showed key-combos are mostly caught quickly!
Also it seems on Arch Linux (I use Arch BTW™) the
keyobject sent through thekeyboard.listenerhas a different shape, or perhaps the inconsistencies in capture behaviors got me jumping to wrong-thinking.Either way, these proposed changes should preserve previously programmed
key.chardetection, while also allowing those stuck with Wayland to enjoy this tool.