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.

Sign up for GitHub

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

Jump to bottom

Support keypress events with non-ascii chars #59

Closed
tomaka opened this issue Nov 3, 2016 · 5 comments
Closed

Support keypress events with non-ascii chars #59

tomaka opened this issue Nov 3, 2016 · 5 comments
Labels
C - needs discussion Direction must be ironed out D - average Likely as difficult as most tasks here H - help wanted Someone please save us P - low Nice to have S - api Design and usability S - enhancement Wouldn't this be the coolest?

Comments

@tomaka
Copy link
Contributor

tomaka commented Nov 3, 2016

Original: rust-windowing/glutin#625
@tomaka tomaka mentioned this issue Nov 3, 2016
Closed
@tomaka tomaka added the S - api Design and usability label Nov 3, 2016
jrmuizel pushed a commit to jrmuizel/winit that referenced this issue Mar 29, 2017
@SimonSapin
Merge pull request rust-windowing#59 from servo/merge
8d02133 
Merge from upstream
@francesca64
Copy link
Member

I'm not really sure what's wanted here. The use case of the person who made the issue originally seems to be best solved using scancodes.

@est31
Copy link
Contributor

est31 commented Dec 24, 2017

Scancodes are hardware dependent. You got no way of printing a name for the key or anything. If you shouldn't use keycodes, why do they exist in the first place?

@tomaka
Copy link
Contributor Author

tomaka commented Dec 24, 2017

The "name of the key" is supposed to be the virtual key code which is reported alongside with the scancode in every event.

@Ralith
Copy link
Contributor

Ralith commented Dec 24, 2017

It would be useful to support querying a human-readable key name from the OS for a given scancode. This would reduce the demand for ridiculously many virtual key codes, and be more convenient/correct for UI purposes besides.

@francesca64 francesca64 added S - enhancement Wouldn't this be the coolest? H - help wanted Someone please save us C - needs discussion Direction must be ironed out D - average Likely as difficult as most tasks here P - low Nice to have labels May 6, 2018
@francesca64 francesca64 mentioned this issue May 28, 2018
Closed
@pyfisch pyfisch mentioned this issue Jan 5, 2019
Closed
@Osspial
Copy link
Contributor

Osspial commented Apr 24, 2019

Closing in favor of #753 and #812

@Osspial Osspial closed this as completed Apr 24, 2019
tmfink pushed a commit to tmfink/winit that referenced this issue Jan 5, 2022
@pcwalton
Add support for the even-odd fill rule in the demo.
c2d89ab 
Closes rust-windowing#59.
madsmtm pushed a commit to madsmtm/winit that referenced this issue Jun 11, 2022
@github-actions @wusyong
publish new versions (rust-windowing#59)
afd1316 
Co-authored-by: wusyong <wusyong@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C - needs discussion Direction must be ironed out D - average Likely as difficult as most tasks here H - help wanted Someone please save us P - low Nice to have S - api Design and usability S - enhancement Wouldn't this be the coolest?
Milestone
No milestone
Development

No branches or pull requests
5 participants
@Ralith @tomaka @francesca64 @est31 @Osspial