Use different event source for special keys #57
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
Signed-off-by: Sahil Nirkhe <[email protected]>
Signed-off-by: Sahil Nirkhe <[email protected]>
stacks13
force-pushed
the
accessibility_keys_fix
branch
from
b6a77a1 to
b45687a
Compare
|
@stweil I have signed off on commits. Please re-run workflow and review |
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.
Issue: #54
Issue was possibly due to the following reasons
Found the fix by trying out some different combinations Event Source and Event Tap
By making use of
kCGEventSourceStateHIDSystemStatefor keys with keyCode > 96, themkey works fine after pressing the these keys: Arrow Keys, Home, End, Insert, Function keys, Page Up/Down