Update ui_qt.cpp
Description
Added the term "Quick Menu", and replaced "Big Picture menu" with "Big Picture menu (not to be confused with Steam's Big Picture mode)"
Related Issues
Fixes:
- https://github.com/libretro/RetroArch/issues/18415
Reviewers
@hizzlekizzle
I don't love the "not to be confused with" bit. If it is confusing, I'd rather drop the "big picture" nomenclature altogether in exchange for "gamepad-friendly interface" or the generic "leanback interface" term.
I'm also not so sure about calling the quick menu a "pause menu." Is that a term that people would be familiar with? Sony calls theirs the "quick menu," too, AFAIK (I think ours predates theirs, though; I believe they first introduced it in 2016, and ours had already existed with that name for a couple of years by then).
Replaced "Quick Menu" and "pause menu" with "Switches the current display between menu and content"
I'm also not so sure about calling the quick menu a "pause menu." Is that a term that people would be familiar with? Sony calls theirs the "quick menu," too, AFAIK (I think ours predates theirs, though; I believe they first introduced it in 2016, and ours had already existed with that name for a couple of years by then).
The Quick Menu documentation lead sentence is: The Quick Menu is effectively RetroArch's pause menu.
However Settings -> Input -> Hotkeys lists
Menu Toggle Switches the current display between menu and content.
Most likely since F1 (or the assigned hotkey) initially opens the Quick Menu but permits navigation to Main Menu, Settings, and others via the back button.
I made a fresh commit to update the documentation with this exact phrasing. Are you ok with it?
Once the (F1) issue has been resolved, I can follow up on the Big Picture term issue.
The "Big Picture" term issue
I don't love the "not to be confused with" bit. If it is confusing, I'd rather drop the "big picture" nomenclature altogether in exchange for "gamepad-friendly interface" or the generic "leanback interface" term.
Proposed terms
The "gamepad-friendly interface" is a good candidate term in my opinion. Below are sections to optional terms that I suggest.
graphical user interface
What do you think about the idea about simply replacing "Big Picture" with the term "graphical user interface (GUI)"? The GUI is navigated with both gamepads and mouse and keyboard. Also, the graphical user interface (GUI) of RetroArch includes menu drivers such as Ozone, XMB, GLUI, and RGUI. In contrast, the Qt-based desktop menu is tailored for mouse and keyboard input and provides a more traditional desktop application experience. This distinction makes it easy for users to recognize the visual differences between the two interfaces.
main interface
Or "main interface"; it is a clear and accurate term for RetroArch's primary menu system, especially since it offers more options and features than the Desktop mode as described in the the dialogue window:
I don't hate calling it the "GUI" or the "main interface", though I believe, technically, the Qt/WIMP UI is also a GUI.
The Main window must remain open for the Desktop Menu window to function; closing the Main window will also close the Desktop Menu window. So perhaps its better to include the term 'window' for clarity when distinguishing between the two open windows: the Desktop menu window and the Main interface window.
What do you think about that?
that seems pretty reasonable to me. As a user, would you be confused if it said that while you're running in fullscreen? (that may not even be possible, exactly, with the WIMP UI in that situation)
that seems pretty reasonable to me.
Great! Please take a look at https://github.com/libretro/RetroArch/pull/18428/commits/e6e0d529ac52230b629ebed7d0ab28718d6c53d6
As a user, would you be confused if it said that while you're running in fullscreen? (that may not even be possible, exactly, with the WIMP UI in that situation)
Fullscreen mode uses a single maximized or borderless window. In the main interface window, press F to enter fullscreen, then F5 to open the WIMP Desktop Menu—this unmaximizes the main interface window and focuses the desktop menu window. You can press F again in the main interface to return to fullscreen (even with the desktop menu window open) and use Tab to switch between the windows.
Added "WIMP (Windows, Icons, Menus, Pointer) (https://github.com/libretro/RetroArch/pull/18428/commits/eecaf7219ac5f48fb7ac84c8e3487c63fa1d63ea) to make it consistent with Settings -> Input -> Hotkeys:
Added the term "Qt-based" to make it consistent with the Desktop Menu's menu bar item: Help -> "About Qt..."
- https://github.com/libretro/RetroArch/pull/18428/commits/4e23d638e65f045662916e3a75b0adf5f2c05e07
I'm not sure that adding the "QT" (should probably be stylized as "Qt" anyway) bit brings much to the table. It's more consistent with the 'help' menu, but I'm not sure that knowing the underlying toolkit name is actually beneficial/desirable for end-users.
I'm not sure that adding the "QT" (should probably be stylized as "Qt" anyway) bit brings much to the table. It's more consistent with the 'help' menu, but I'm not sure that knowing the underlying toolkit name is actually beneficial/desirable for end-users.
- I have already changed it to "Qt"
- RetroArch generates retroarch_qt.cfg for Desktop Mode and retroarch.cfg for the main interface window. This provides users a clear way to distinguish Desktop Mode—in addition to WIMP terminology.
Clarify that the hotkey examples reflect the default key assignments, as users with custom mappings may find the examples don’t match their setup.
- https://github.com/libretro/RetroArch/pull/18428/commits/c110caae5d23afb9f13af472ac44151ada166443#diff-dde6cbee432684fe02047f607aed200aa9b914b9f280b6dc6042aea995f98fc2R1839
Added 'View ->' before 'Settings -> Input -> Hotkeys' to show these settings are accessible from the Desktop Mode window.
- https://github.com/libretro/RetroArch/pull/18428/commits/f74920c3121fc7368ee18988583b55ef55dec3e0