[Feature request] Show broken button mappings
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
Expected behavior
RetroArch could display the value in red text to indicate that it does not work as expected.
Actual behavior
Even if the OS drivers don't support the controller, for example if a value is set to "0", RetroArch doesn't warn that the controller is not supported.
Example of non-supported controller:
- With Sony DualSense in Fairphone 4 with Android 12, RetroArch "R Button (Shoulder)" receives the value "0".
Steps to reproduce the bug
Map buttons in "Settings -> Input -> RetroPad Binds -> Port 1 Controls" with a controller that is not supported by the OS.
Bisect Results
[Try to bisect and tell us when this started happening]
Version/Commit
You can find this information under Information/System Information
- RetroArch: [version/commit]
Environment information
- OS: [The operating system you're running]
- Compiler: [In case you are running local builds]
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 in Settings -> Input -> RetroPad Binds -> Port 1 Controls and trace how button mappings are displayed, focusing on the value "0" for unsupported controller inputs. Done means RetroArch visibly marks broken mappings, such as with red text, while preserving normal mappings.
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