Android touch controls in the playlist image zoom enhancement
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Describe the problem
RetroArch menu default in android is to hide the overlay and control the menus with touch controls. But the playlist is less featureful than a desktop or a controller controlled RA because you can't select without pointing and clicking. It's no big deal in the playlist itself since drag works, but if you want to see game covers or other images (long press the images or text if available), you can't move up or down like in the desktop, just tap to exit the zoom.
Suggested change
In android, when in the game image zoom state and you don't have a controller connected, define some buttons to progress up\down the playlist and some for cycling the images like a button can do in the desktop.
Alternatively, implement up down gestures to do the same more "naturally" for android, and tap anywhere to exit (no change). This also opens the possibility to use the left-right axis to cycle through the 3 images (using the settings defined elsewhere for what images appear in the zoom).
Using the overlay in the menus is not a good solution at all because it's quite disruptive, not a alternative to close this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating RetroArch's Android playlist image-zoom state and its touch-input handling, then compare the desktop or controller behavior for playlist movement and image cycling. Done means Android users without a connected controller can move through the playlist and cycle images with defined buttons or gestures while tapping still exits zoom.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- frontend, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100