Input/Hotkeys are locked in QWERTY
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
When binding/rebinding inputs under the 'Input' menu, Retroarch behaves as if the keyboard is in the QWERTY layout, even if it is set to a different layout in the OS. Searching (with /) is not affected.
For example, 'Fullscreen Toggle' is bound to F by default. Pressing my F key doesn't do anything since it is mapped to my right hand in my layout. Pressing the T key works, however, since my T is where QWERTY's F is (left hand, index finger, home row).
I can manually bind fullscreen to my F key, but the menu shows it bound to U instead, since QWERTY's U is where my F is. This is a reasonable workaround but would make rebinding confusing. It also initializes all the shortcuts to the wrong keys by default. (This is debatable--control keys [z,x,c etc] are chosen based on position, so should depend on physical position, not legend, but most other keys have mnemonics [f for fullscreen, m for mute etc], so should map to a specific letter).
Tested with a default config. To reproduce, set a non-QWERTY layout and bind some keys to test one-by-one; the top row will spell out QWERTY no matter what.
Bisect
Highly likely related to #8303. This used to work, but I hadn't used RA on a machine with a non-QWERTY layout in a while. I don't have a build environment set up but I could if it's necessary.
Environment
- RetroArch: 1.8.4 9e25601
- OS: Kubuntu 19.10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from RetroArch's Input menu and compare its key binding behavior with the non-QWERTY OS layout described here; review related issue #8303 for historical context. Done means bindings and default shortcuts use the intended physical or labeled keys consistently instead of assuming QWERTY.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100