Skip to content

Add 'Menu Toggle Without Hotkey Enable' option#18785

Open
BrandonKowalski wants to merge 1 commit intolibretro:masterfrom
BrandonKowalski:feature/menu-toggle-ignore-enable-hotkey
Open

Add 'Menu Toggle Without Hotkey Enable' option#18785
BrandonKowalski wants to merge 1 commit intolibretro:masterfrom
BrandonKowalski:feature/menu-toggle-ignore-enable-hotkey

Conversation

@BrandonKowalski
Copy link
Copy Markdown

@BrandonKowalski BrandonKowalski commented Mar 1, 2026

Summary

Adds a new option under Settings > Input > Hotkeys that allows Menu Toggle to bypass the Enable Hotkey modifier.

Handheld users (Retroid, Anbernic, etc.) with a dedicated menu/back button can enable this so Menu Toggle works without holding Enable Hotkey, while all other hotkeys still respect it.

Addresses #18396

Test Plan Checklist

  • Build RetroArch and confirm no compilation errors
  • Settings > Input > Hotkeys shows the new "Menu Toggle Without Hotkey Enable" toggle
  • With Enable Hotkey set to SELECT and Menu Toggle set to a different button:
    • Setting OFF: Menu Toggle requires SELECT held (current behavior)
    • Setting ON: Menu Toggle works alone; other hotkeys still require SELECT

Thanks for considering! Appreciate everything you do to make this hobby so awesome!

Adds a new boolean setting that allows Menu Toggle to bypass the
Enable Hotkey modifier. Handheld users with a dedicated menu button
can enable this so Menu Toggle works without holding Enable Hotkey,
while all other hotkeys still respect it.

May fix libretro#18396
@hizzlekizzle
Copy link
Copy Markdown
Collaborator

hizzlekizzle commented Mar 1, 2026

I'm personally not a fan of this, not because I don't think the functionality is good, but because there will instantly be requests for a bypass for fast-forward (that is, most of the requests for this I've seen are for menu and FF), so we'd need a setting for that, too. I don't imagine it will stop there, either, unfortunately, and I don't think adding a separate bypass for every hotkey (or even a significant percentage of them) is sustainable.

@BrandonKowalski
Copy link
Copy Markdown
Author

BrandonKowalski commented Mar 1, 2026

I understand the concern about the slippery slope. My perspective (for whatever it's worth 🤣) is that this PR restores functionality that was present, albeit unintentionally, in RetroArch prior to version 1.22.0.

That said, Menu Toggle is arguably unique. On many handheld devices menu is a dedicated physical button. Fast-forward and others don't share that same hardware justification, which could serve as a reasonable line to hold.

@hizzlekizzle
Copy link
Copy Markdown
Collaborator

yeah, that's the same reasoning we use for allowing menu_toggle into the autoconfig profiles. we can see what others think about it. I'm not dead-set against it, so if others are into it, I won't try to torpedo it :)

@LibretroAdmin
Copy link
Copy Markdown
Contributor

I don't really mind if it gets merged. I guess we can ask @warmenhoven as well

@cmitu
Copy link
Copy Markdown
Contributor

cmitu commented Mar 2, 2026

That said, Menu Toggle is arguably unique. On many handheld devices menu is a dedicated physical button. Fast-forward and others don't share that same hardware justification, which could serve as a reasonable line to hold.

I think this is also true for some configuration used in arcade cabinets, where users can reserve a dedicated key (usually mapped to tab for MAME) to open the (configuration) menu.

@josegonzalez
Copy link
Copy Markdown

Any chance this could get merged? Most of my retro devices run some form of Retroarch, and being able to trigger the menu toggle without needing two buttons would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants