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

Keyboard settings depends on system default keyboard layout #3452

Closed
Psycho-A opened this issue Sep 16, 2017 · 8 comments
Closed

Keyboard settings depends on system default keyboard layout #3452

Psycho-A opened this issue Sep 16, 2017 · 8 comments
Labels

Comments

@Psycho-A
Copy link

If we use some non-latin language (like Cyrillic) in keyboard layout by default, the emulator tries to use their local keycodes instead of universal (English) ones. As a result, buttons configured with English system language, doesn't work when we changed layout to non-english, or just transfer our settings to other PC. This is really annoyingly and looks like omission.

@Megamouse
Copy link
Contributor

I might have a fix for this once i get home.

@Psycho-A
Copy link
Author

Psycho-A commented Nov 29, 2017

@Megamouse, it would be nice, as we don't need to have separate configs for different keyboard layouts!

@dio-gh
Copy link
Contributor

dio-gh commented Oct 8, 2019

This is an amazing edge case, damn. :p Probably still an issue, needs retesting. as there was absolutely nothing done about it in 2 years.

@Megamouse
Copy link
Contributor

It doesn't need retesting as we changed absolutely nothing about it. It would be a miracle if it suddenly worked

@gamingrobot
Copy link
Contributor

Citra has an issue open around the same issue https://github.com/citra-emu/citra/issues/4243
This library was linked in the comments and describes the problem and a possible solution https://github.com/nyanpasu64/qkeycode

@Megamouse
Copy link
Contributor

This probably needs to be re-tested.

@Megamouse
Copy link
Contributor

Closing due to inactivity

@Psycho-A
Copy link
Author

This probably needs to be re-tested.

The problem still persists.

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

No branches or pull requests

5 participants