libretro / libretro/RetroArch

[Bug] Touchscreen inputs fail to register on bottom screen when manually toggled in 'Top only' layout

Open
#19,146 0 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

Is there an existing issue for this?
  • This is a bug in RetroArch frontend
  • I have searched the existing issues
Description

Description

When the screen layout is configured to "Top only", manually switching/toggling the view to the bottom screen causes the Nintendo DS touchscreen functionality to break. The emulator stops registering any touch or mouse click inputs on the bottom screen.

Environment / Platforms Tested

  • Core: melonDS (Latest version)

Actual Behavior

The bottom screen becomes completely unresponsive to touch inputs once it is toggled into view under the "Top only" layout constraint.

Expected behavior

Expected Behavior

When toggling to the bottom screen in "Top only" mode, touch inputs should adapt and remain functional for that screen.

Steps to reproduce the bug

Steps to Reproduce

  1. Launch a Nintendo DS game using the melonDS core.
  2. Go to Quick Menu -> Core Options -> Screen and set the Screen Layout to Top only.
  3. Use the mapped hotkey to toggle/swap the screen view so that the Bottom Screen is now displayed.
  4. Attempt to interact with the bottom screen using touch inputs (or mouse clicks on PC).
  5. Notice that the game does not respond to any touch or tap inputs.
Version/Commit

1.22.2

Bisect Results

No response

Present in the nightly version

Yes, this is reproduced in the nightly build

Platform & operating system
  • Nintendo Switch: Atmosphere CFW (Console touchscreen input) * PC: Windows 10/11 (Mouse clicks as touch input) * Android: Android 13/14 (Direct touchscreen input)
Affected Cores

No response

Environment information

No response

Relevant log output

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

Reproduce with the melonDS core using Core Options > Screen > Screen Layout: Top only, then toggle to the Bottom Screen and test touch or mouse input on the listed platforms. Trace the frontend's screen-toggle and touchscreen input handling; done means bottom-screen interaction remains responsive after the view is toggled.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.