Hotkey binding not working correctly
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
Hotkey binding on Android is not working correctly.
Expected behavior
I should be able to bind the A and B buttons as Hotkeys and still use them to navigate through the menu system.
Actual behavior
If I try to bind either the A or B button on a Razer Kishi or an Xbox One controller to a Hotkey, I can no longer navigate in the menus until I remove the binding. This happens even with a Hotkey Enable key setup.
Steps to reproduce the bug
Bind the A or B keys to a Hotkey and see that you will no longer be able to move forward or back in the menu system, depending on which button you have bound.
Version/Commit
- RetroArch: 1.9.8/b2c87baa
Environment information
- OS: Android 11 on Google Pixel 3XL
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
Reproduce the issue on Android 11 with a Razer Kishi or Xbox One controller, binding A or B as a hotkey with a Hotkey Enable key configured. Trace the hotkey and menu-navigation input handling; done when either binding no longer prevents forward or back navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100