Repository navigation
native/macos: Fix key up events when command key is pressed - #626
Merged
Merged
Conversation
…s are swallowd. Co-authored-by: Copilot <copilot@github.com>
Owner
|
Thanks for PR! |
Contributor
Author
|
Thanks for the merge! |
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.
On macOS when the command key (super key) is pressed all KeyUp events are swallowed until the command key is released again. So when you press COMMAND + you get a KeyDown event for both COMMAND and , but when you release both keys again you only get a KeyUp event for the COMMAND key.
This is fixed by faking these events ourselves. In the main loop (the run function) we already trap the raw event. We use this event to generate KeyUp events.
Closes not-fl3/macroquad#980