libretro / libretro/RetroArch

Assigning rewind to an axis re-enables the default rewind hotkey

Open
#15,930 0 comments 0 reactions 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

When rewind has a default button, but rewind is only bound to an axis, pressing its default button will invoke rewind even if that button is bound to a different action.

Expected behavior

Only explicitly bound actions trigger when a button is pressed. If the menu says rewind is only bound to an axis, only that axis should trigger it.

Actual behavior

See description.

For instance, in my distribution, rewind is bound to Button 6 by default. If I assign rewind to Axis +2 and press button 6 or Axis +2, rewind is invoked.
Re-assigning rewind from an axis to a different button (i.e. button 7) fixes the problem, and button 6 no longer triggers a rewind.

Steps to reproduce the bug
  1. Assign rewind button to an axis
  2. Press the default rewind hotkey in-game
Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.16.0 f091b5a9e9
Environment information
  • OS: unix ARMv8

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 by reproducing the issue in RetroArch 1.16.0 on the reported Unix ARMv8 environment, then trace the input-binding and rewind hotkey handling. Done means assigning rewind to Axis +2 triggers it only from that axis, while the former default button no longer invokes rewind; the payload does not name a source file or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.