-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
I was making a Nintendo DS overlay and when testing the overlay I noticed that the touch input in the bottom screen was not working as intended, I tested with the default Retropad overlay and that worked fine, the problem is when an overlay have an big element like a background and the size of it covers the area of the emulating content, even if the overlay have a fully transparent area for the screen Retroarch nulls any touch input for it.
bug.demonstration.mp4
Expected behavior
Having the touch screen working entirely in the bottom screen of the emulated Nintendo DS and the overlay itself even if the background virtually covers the entire screen, overlays like Retropad aren't affected by this because they are buttons-only overlays and doesn't have anything like a background covering the entire screen
Steps to reproduce the bug
1 Load any Nintendo DS content that uses touch input
2 Use a custom overlay with a fullscreen background
3 If the overlay virtually covers the entire screen with something like a background the overlay nulls the touch input from being registered in the emulated content
Version/Commit
1.21.0
Bisect Results
No response
Present in the nightly version
Yes, this is reproduced in the nightly build
Platform & operating system
Android 10, Android 13
Affected Cores
melonDS 0.9.3, melonDS DS 1.2.0, NooDS b0f658c
Environment information
No response