Skip to content
New issue

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

Support ScanCode input bindings #179

Closed
alice-i-cecile opened this issue Jul 15, 2022 · 1 comment · Fixed by #312
Closed

Support ScanCode input bindings #179

alice-i-cecile opened this issue Jul 15, 2022 · 1 comment · Fixed by #312
Labels
enhancement New feature or request

Comments

@alice-i-cecile
Copy link
Contributor

alice-i-cecile commented Jul 15, 2022

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

@alice-i-cecile alice-i-cecile added the enhancement New feature or request label Jul 15, 2022
@alice-i-cecile
Copy link
Contributor Author

See also: bevyengine/bevy#5495

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant