We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bind to actions based on the scancode sent. These correspond to the semantic values of keys, not just their position on the keyboard.
As a result, these are essential to supporting non-US keyboards (and for text entry).
Add an InputKind variant that supports this.
InputKind
In order to handle this correctly, we'll need to parse the keyboard event streams themselves.
Assigning semantic value is out of scope for a first attempt; ideally this is handled at the winit level: rust-windowing/winit#1904
See bevyengine/bevy#2052 and bevyengine/bevy#862 for upstream work in Bevy.
More discussion in winit: rust-windowing/winit#753
The text was updated successfully, but these errors were encountered:
See also: bevyengine/bevy#5495
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
What problem does this solve?
Bind to actions based on the scancode sent. These correspond to the semantic values of keys, not just their position on the keyboard.
As a result, these are essential to supporting non-US keyboards (and for text entry).
What solution would you like?
Add an
InputKind
variant that supports this.[Optional] How could this be implemented?
In order to handle this correctly, we'll need to parse the keyboard event streams themselves.
[Optional] What alternatives have you considered?
Assigning semantic value is out of scope for a first attempt; ideally this is handled at the winit level: rust-windowing/winit#1904
Related work
See bevyengine/bevy#2052 and bevyengine/bevy#862 for upstream work in Bevy.
More discussion in winit: rust-windowing/winit#753
The text was updated successfully, but these errors were encountered: