Expose physical keys #2523
Closed
Expose physical keys #2523
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.
Expose winit physical keys, aka native key codes. Useful for shortcuts that a based on actual position of keys.
The data model basically just a copy from winit with some changes:
unreachable!()in conversion function because of non_exhaustive, there is non_exhaustive_omitted_patterns lint which could help, but it is nightly-only#![allow(missing_docs)]on top of fileAlternative would be to re-export types from winit. Let me know which one do you prefer.winit is abstracted away