[Feature Request] Short “Hotkey Enabled” timer to prevent unintended inputs [INPUTREWRITE]
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating RetroArch’s handling for the Select, Start, Home, L3, and R3 buttons and the Hotkey Enabled state. Trace where button-down input reaches the running game and where button-up and hotkey state changes are processed. The issue does not identify files or tests; success means short presses pass through while qualifying held presses activate the hotkey state, with the delay behaving consistently.
Written by the indexing model from the issue text.
Description
The Hotkey Enabled button has no way to block normal inputs. It does for the buttons assigned to specific actions but not the modifier that puts it into the hotkey input state. If you assign it to Select for example, the running game will insert a coin, bring up a menu, etc. while you hit a hotkey.
Would it be possible to change how the button assigned as the modifier registers input? Instead of it being read on button down, set a timer before a button up state. A normal press can be passed to the game if it’s held for less than say .2 seconds. Held longer and the Hotkey Enabled state takes effect. It should feel natural and intentional with the default delay.
It wouldn’t make sense for the main face buttons so limit it to Select, Start and Home buttons. Possibly L3 and R3 too since they are not used as often.
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 2.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 63
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from libretro/RetroArch
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
libretro/RetroArch#20108 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/RetroArch#20061 · 3 comments ·
Maintainers usually reply within 2 days
-
[Feature Request] [UX] Improve descriptions for "Rewind Buffer Size" and "Rewind Buffer Size Step"Openfeature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
libretro/RetroArch#19915 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
All issues in libretro/RetroArch
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
schrodinger/pymol-open-source#532 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
facebookexperimental/hermit#347 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
CTSRD-CHERI/cheribsd#2769 ·
Maintainers usually reply within 2 days
-
good first issue not started
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
CU-Robotics/firmware#257 ·
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100