libretro / libretro/RetroArch

[Feature request] Quit RetroArch: Display "Saved new config to [config directory]/retroarch.cfg" before the program closes

Open
#16,094 5 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

Expected behavior
  • Settings -> Configuration -> Save Configuration on Quit -- should display "Saved new config to [config directory]/retroarch.cfg". The message could be visible for about 2 seconds (because that is how long they are visible when RA is open) before the program quit, in order to inform the user.
Actual behavior
  • Settings -> Configuration -> Save Configuration on Quit -- does not display "Saved new config to [config directory]/retroarch.cfg"
Steps to reproduce the bug
  • Main Menu -> Settings -> Configuration File -> Save Current Configuration -- displays "Saved new config to [config directory]/retroarch.cfg". The message is visible for about 4 seconds.

Screenshot from Android:
image

  • Settings -> Configuration -> Save Configuration on Quit -- does not display the above message
Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.17.0 apk from retroarch.com
Environment information
  • OS: Android

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

Trace the Save Configuration on Quit path and compare it with Save Current Configuration, which already displays the requested message. Done means the save-on-quit flow shows the configuration path for about two seconds before RetroArch closes, including the Android case described.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.