libretro / libretro/RetroArch

[Feature Request] Native image viewer

Open
#12,631 1 comment 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

Hello
I'm using RetroArch 1.9.4 in Lakka 3.1 on RaspberryPi4B
I wish to ask for a enhancement.
I was playing with the Images feature (the playlist Images), figuring out how it works. As far as I can see, in order to view/show an image RetroArch is using a "pseudo-core". This means that before opening an image any other running core/content has to be closed (because only one content can be loaded at the same time)
Use case: I am playing a RPG game and I have the maps of the game also in Lakka. I would like to be able to pause the game (without closing the content... just "quick menu"), navigate to the Images, consult the map, and return to the game.
Until now, as I said, the game is ended as soon as the map is opened. This is what I would like to avoid.

I know that I can save a state, close the game, consult the map, re-run the game and load the state... But I would like something more... seamless

I just suggest to use a native image viewer, directly managed by the OS. Consequently, avoiding using a "pseudo-core" and leaving libreto/retroarch in stand by

A workaround: actually the image is previewed as a thumbnail as usual, but if you think about my use case, this is not practical. I mean, the map of a RPG game is usually very large and you will see nothing in a preview. Probably, in this "native image viewer", you need a magnifier feature indeed...

Thak you so much!

P.S: this post is a fork from https://github.com/libretro/Lakka-LibreELEC/issues/1422 They suggested me to put it here too

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 RetroArch's Images playlist and the pseudo-core flow described in the issue. Define how a native image viewer would coexist with paused game content, including viewing large maps with magnification. Done means an image can be opened and consulted without closing the active game, then exited back to it.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.