Am I able to make a single button map to the Quick Menu said in Enabling in-game Quick Menu: And finally, I'm still trying to figure out how to map the extra keys on my control panel to do what I want.My Xbox360 controllers also have no key mapped to start a game, but the docs page makes me think it should be pretty automatic.Or did my remapping for one device reset it for others? I tried remapping my keyboard hotkey to be "rshift" but now I notice that my Xbox360 controllers have the ability to bring up the Quick Menu, but maybe that was previously broken.f I have a game-specific config, does the system-level config load and then get overridden on some parameters by the game-specific one? Or is the game-specific one loaded instead of the system one?.I'm mostly asking if anyone has any detail beyond the Controller sub-pages of the RetroPie docs that describes how the various layers of configs override one another. Yes now that I can get the quick menu working I can change some things, but others require what appears to be manual edits. Otherwise, the text could be shorter than the original while still being more descriptive.Thanks. I am not sure the description needs the technical verbiage "implements frontend keyboard callback functionality" but I left it in to err on the side of conservatism. When set to 'Detect', option will be enabled if current core implements frontend keyboard callback functionality. Here is my 217 character edit (+34 over the current text):ĭisable Retroarch hotkeys for core use when launching or resuming content. ![]() The current one is 183 characters:Īlways enable 'Game Focus' mode when launching and resuming content. These options are longer but still understandable at a glance, while suggesting the user has switched control contexts.ģ) The Input menu description. (keyboard icon) Core using keyboard: Hotkeys disabled I would consider renaming it, like "Keyboard: Core Focus" or "Core keyboard: Game Focus." "Game Focus" is not wrong, but it's vague, easily confused with the important gaming term "Game Mode," and arguably not accurate enough as it impacts the frontend and the core, not individual games. I have a question - Is this specifically focused on cores accessing keyboards? The text in the Input option menu suggests so, so just using the word "keyboard" more would be okay.ġ) The option name. I don't think improving this specific function leads RA down a slippery slope of tedious overwritten descriptions for the mundane, and this seems not super related to the meta-question of how the RA menus should be organized, which I know is still a hot topic. RA's design precludes some of the standard UX approaches to context switching (like tabs). This is a special case among RA options in that it's a context switch for the user interface. The fair number of upvotes here (thanks!), in my first post to the sub, shows this is still news to many RA users. Before writing the OP, I searched for '"quick menu" disabled retroarch' and the results were less relevant. People complained then that they hadn't had any inkling the feature existed, or felt it wasn't visible enough. The top result is a reddit post from last year. I searched Google for '"Game Focus" Retroarch'. I also want to note my research - as it stands, the option is a missed opportunity for users. I also think the ingame notifications are a close second. ![]() tl:dr - the most important one is 3) at the bottom, the menu description. ![]() Thanks for explaining things and listening to my views :)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |