libretro / libretro/RetroArch

Suggestion: Offer alternative "input_face_" variables

Open
#16,329 1 comment 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

It's difficult to remember the position of the face buttons ("A" "B" "X" "Y"). To make it simple to figure out the position and to make it consistent with D-PAD (input_up_btn, input_down_btn, input_left_btn, input_right_btn), I suggest that RA is compatible with an additional set.

Proposed extra set

I recommend that this set is used by default by RetroArch, and its autoconfig file.

input_face_down_btn
input_face_left_btn
input_face_right_btn
input_face_up_btn

input_face_down_btn_label = "Face Button Down"
input_face_left_btn_label = "Face Button Left"
input_face_right_btn_label = "Face Button Right"
input_face_up_btn_label = "Face Button Up"

input_face_down_axis
input_face_left_axis
input_face_right_axis
input_face_up_axis

input_face_down_axis_label = "Face Button Down"
input_face_left_axis_label = "Face Button Left"
input_face_right_axis_label = "Face Button Right"
input_face_up_axis_label = "Face Button Up"

Current set

The (old) set can still be used in RA.

input_b_btn
input_y_btn
input_a_btn
input_x_btn

input_b_btn_label = "B"
input_y_btn_label = "Y"
input_a_btn_label = "A"
input_x_btn_label = "X"

input_b_axis
input_y_axis
input_a_axis
input_x_axis

input_b_btn_axis = "B"
input_y_btn_axis = "Y"
input_a_btn_axis = "A"
input_x_btn_axis = "X"

See also

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 tracing RetroArch's input configuration and autoconfig handling for the existing input_a_btn, input_b_btn, input_x_btn, and input_y_btn variables. Compare that path with the proposed input_face_* button and axis names, then verify that the new aliases and labels work while the existing names remain supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
game-dev
Issue type
Feature
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.