libretro / libretro/RetroArch

Binding keys UI is unfriendly

Open
#10,337 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

This appears to be the proper place, but let me know if it belongs elsewhere.

User is expected to divine the proper incantation to unbind a hotkey through their closeness with god (or something).

User is able to bind multiple keys to conflicting actions.

Expected behavior

The UI for any page where a user binds keys should inform the user of how to unbind keys.

Attempting to bind a key to multiple actions within the same menu should unbind the key from other actions in the same menu.

Actual behavior

The user is provided helpful d-pad icons about "OK" "Search" and "Back" (In ozone, all other GUIs expect you to know how search, unbind, reset, and every other feature already work)

The user can bind every action to escape if they so please. Maybe this is a "feature", but the claim is that its unfriendly.

Steps to reproduce the bug

Go to any menu where hotkeys are bound. For example "Hotkey Binds"

Bisect Results

No bisection occurred.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.8.5
Environment information
  • OS: Linux (Arch)
  • Compiler: [In case you are running local builds]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the RetroArch "Hotkey Binds" menu and reproduce the conflicting-binding behavior described in the issue. Trace the UI path used by pages where hotkeys are bound; done means the interface explains how to unbind keys and assigning a key to one action removes it from other actions in the same menu.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.