libretro / libretro/RetroArch

[Feature request] Make the "Quick Menu" available after "Main Menu -> Load Core -> [Any core]"

Open
#16,127 2 comments 0 reactions 0 assignees View on GitHub

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

Please also read my slightly different solution of my feature request:

Expected behavior (feature request)

My feature request is that the Quick Menu becomes visible, specifically "Quick Menu -> Core Options" so you don't have to run:

  • Main Menu -> Load Content -> [Any game] -> [Any core] -- needed to access the Quick Menu
  • Quick Menu -> Core Options -- Here's the example of bsnes-hd beta:

image

Actual behavior

The Quick Menu does not become available.

Steps to reproduce the issue
  • Main Menu -> Load Core -> [Any core]
Bisect Results

[Try to bisect and tell us when this started happening]

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.16.0
Environment information
  • OS: Any
  • Compiler: [In case you are running local builds]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Main Menu -> Load Core -> [Any core] path in RetroArch 1.16.0 and compare it with loading content, which exposes Quick Menu -> Core Options. Review the related proposal in issue #16125 and determine the expected behavior before changing anything; done means the Quick Menu is available after loading any core without content.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.