Reconfiguration needed on connect/disconnect joypads

Open
#13,180 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
game-dev

Research direction

No source file, test, or entry point is named. Start by tracing joypad connection and disconnection handling, controller ordering, and device-to-button-mapping storage. Done means a newly connected joypad is appended and changing controller order preserves each device's mappings; add or update coverage for both behaviors.

Written by the indexing model from the issue text.

Description

input joypad autoconfig

Use Case example:

Steps:
  • Connect 2 joypads.
  • Set controller order (which is the first and which is the second).
  • Configure button mappings for each joypad.
  • Play any 2 players game.
  • Connect one more joypad to play a 3 player game.
Observed behavior
  • Retroarch don't preserve joypad order (seems to shuffle).
  • If changing joypad order, the button mappings must be reconfigured.
Desired behavior
  • Put new connected joypad as last on controllers list.
  • Track button mapping to device, helping to change the order of joypads without button mapping reconfiguration.
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

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.

More from libretro/RetroArch

All issues in libretro/RetroArch

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.