libretro / libretro/RetroArch

[Feature Request] Standardized status icons and omission of status text for osd/notifications file operations

Open
#19,252 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Currently, RetroArch provides feedback for successful file operations, but lacks clear error indicators when operations fail. Examples of this inconsistency include:

  • Core Downloader: Online Updater → Core Downloader → [any core] shows a green check mark and says Extracting '[core].zip' upon success, but provides no red cross icon if the extraction fails.
  • Remap Files: Controls → Manage Remap Files → Save Remap File As displays Remap file saved successfully. upon success, but does not provide an explicit message or notification if it fails.

Proposed Solution:
Standardize all file operations to follow a consistent feedback format:

[Status Icon] [Notification text]

  • Examples:
  • Success: [Green Check Mark] Extracting core.zip / Saved remap_file.rmp
  • Failure: [Red Cross / Error Icon] Extracting core.zip / Saving remap_file.rmp

This approach saves translations (by avoiding words like "Successfully" or "Failed") and grammar variations (by avoiding mixed tenses like "Extracted" versus "Extract"). It ensures users receive immediate, unambiguous confirmation of both successful and failed file-system interactions across the entire interface.

File operation menu items

All these menu items are affected by this feature request.

Main Menu

Playlists -> Explore -> Show All -> Save as View

Online Updater -> Core Downloader

Online Updater -> Update Assets

Online Updater -> Update Controller Profiles

Online Updater -> Update Cheats

Online Updater -> Update Databases

Online Updater -> Update Overlays

Online Updater -> Update GLSL Shaders

Configuration File -> Save Current Configuration

Configuration File -> Save New Configuration

Configuration File -> Save Configuration As

Quick Menu

Save States -> Save State

Save States -> Load State

Core Options -> Manage Core Options -> Save Game Options

Core Options -> Manage Core Options -> Remove Game Options

Core Options -> Manage Core Options -> Save Content Directory Options

Core Options -> Manage Core Options -> Save Content Directory Options

Controls -> Manage Remap Files -> Save Remap File As

Controls -> Manage Remap Files -> Save Game Remap File

Controls -> Manage Remap Files -> Remove Game Remap File

Controls -> Manage Remap Files -> Save Content Directory Remap File

Controls -> Manage Remap Files -> Remove Content Directory Remap File

Controls -> Manage Remap Files -> Save Core Remap File

Controls -> Manage Remap Files -> Remove Core Remap File

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 tracing the listed Main Menu and Quick Menu operations, using the Core Downloader and Remap Files examples as references for existing feedback. Inventory how each operation reports success and failure, then verify that all listed file operations use a consistent status-icon and notification-text format.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.