[Feature Request] Quick"-er" Menu
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
First and foremost consider this:
- Only RetroArch bugs should be filed here. Not core bugs or game bugs
- This is not a forum or a help section, this is strictly developer oriented
Description
One thing i love about the older GUI based emulators, such as the GX emulators on the wii or nintendo's official offerings, is their extremely minimalist quick menus that usually only pertain to the actual gameplay. This allowed me to recommend them easily to the younger or less experienced when I felt that getting them to memorize multiple hotkeys was too much.
I propose an idea where if the menu hotkey is quickly pressed, it brings up this menu. But if it's held down, it brings up the full "regular" quick menu/menu. The only options it would consist of are quick save state, quick load state, rewind (slo-mo if it's disabled), and fast foward.
This can be organized in any way (even the Wii GX way where there's one in each corner), but what I imagine is somthing like a tv remote: A cross configuration, with rewind/slo-mo on the right, fast foward on the left, save on top, load on the bottom. Whatever the dpad or right analog stick is pointing toward when they hit the hotkey again will be what occurs. Like an over simplified weapon wheel.
I think this can go a long way toward usability, especially in a retro handheld, mobile, or external frontend setup (think emulationstation).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating RetroArch’s existing quick-menu and menu-hotkey handling, then clarify the tap-versus-hold interaction and selection behavior; done means a quick press exposes the proposed gameplay actions while a held press retains the regular menu.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100