[Feature Request] INPUT: Option to ignore Enable Hotkey for the Menu Toggle hotkey.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Related to the second issue in the following: https://github.com/libretro/RetroArch/issues/18393
RetroArch 1.22 "broke" the way menu toggling works by strictly enforcing the Enable Hotkey being required to use the Menu Toggle key.
I put broke in quotes because I believe the way it is now has always been the way it was intended, but for whatever reason, at least on handhelds such as the Retroid, the Menu Toggle has always ignored the Enable Hotkey and just worked.
For instance, if I press the back button on my Retroid (or menu buttons on my other handhelds), the RA menu pops up. But using functions such as rewind and fast forward requires me to hold SELECT.
I'd like to request an option be added - something like "Ignore Enable Hotkey for Menu" to input settings.
This way, we get the best of both worlds.
I love the option to have both the Hotkey Enable and Menu Toggle on the same button.
The only thing is - at least on handhelds - usually the menu button is close to the analog/dpad so makes things like fast forward and walking difficult if it were also set to Enable Hotkey.
That's about it. Thanks for everything you guys!
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 by reading the second issue linked from issue 18393 and trace RetroArch's existing Menu Toggle and Enable Hotkey behavior. No files or tests are named in this issue. Done means an input setting allows Menu Toggle to work without Enable Hotkey while preserving the current behavior for other hotkey functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100