Use A-Button for all menus, not "Button 0"
-
I understand the current text-based menu system is not going to change, but is it possible to change the default button configuration for those menus? For example, in the documentation of the runcommand menu:
https://github.com/retropie/retropie-setup/wiki/runcommandIt says:
"This is accessed by pressing any key on the keyboard or button 0 on a joystick (what is the button 0 vary depending on the gamepad used)"Would it be possible to change this hard-coded use of button 0, and to use the user-defined button A? While at it, why not also change the directional controls of this menu to always honor the user-mapped directional controls on the controller?
After the user maps a controller in ES, ES already writes the mappings to all kinds of config files. So why not write one more file for the text-based menus. Then all the text-based menus could check for this file. If it exists and contains a valid mapping for button A and/or the directions, then those mappings are used to control the menu, instead of button 0 and analog joystick directions.
This would make the navigation of all menus much more consistent. I would say this is a prerequisite for a somewhat intuitive menu navigation.
-
@rsn8887 the a button does work in those menus already now.
-
Yes, I just took a look at joy2key.py
https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/supplementary/runcommand/joy2key.py
and it seems this was fixed already, it reads the user-mapping from Retroarch config! My system is just too old, 4.1, I will upgrade and test again.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.