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

Add additional ImGuiKey entry for the extra key on a non-US ISO keyboard, and add a case for it to the Win32 backend. #7206

Closed

Conversation

tom-seddon
Copy link
Contributor

As ImGuiKey values are named after keys on a US keyboard, this key is not named after what's on its keycap - since US keyboards don't have it! (And the character this key produces in practice varies...)

See #7136

…ard, and add a case for it to the Win32 backend.

As ImGuiKey values are named after keys on a US keyboard, this key is not named after what's on its keycap - since US keyboards don't have it! (And the character this key produces in practice varies...)

(cherry picked from commit 7decc97)
@ocornut
Copy link
Owner

ocornut commented Feb 14, 2024

I am going to close this, seeing that according to https://docs.google.com/spreadsheets/d/1TwAHusBpxf_avmk03FUSrni17RP8qXmbJeDzs5fs0nY/edit#gid=0 we have many other things to tackle and they would be best tackled together.

Additionally, afaik according to data we have (please confirm), VK_OEM_8 key referred to in this PR never correspond to a key that doesn't exist in physical US layout. It is also that the mapping of GraveAccent is confusing depending on layout.

@ocornut ocornut closed this Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants