libretro / libretro/RetroArch

Mouse Support in menu when "Hide Overlay in Menu" is set to Off

Open
#14,688 2 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

Description

Control of the menu with the mouse no longer functional when an overlay is selected, and "Hide Overlay in Menu" is set to off.

The mouse apparently gets removed from the RetroArch environment, switching back to controlling Windows. When setting "Hide Overlay in Menu" to Off with an overlay selected, the mouse cursor changes from the RetroArch look back to the regular windows cursor and can no longer control the menu.

Expected behavior

The menu should be controllable with the mouse regardless of the "On-Screen Display" options.

Actual behavior

The menu isn't controllable with the mouse once an overlay is selected and "Hide Overlay in Menu" is set to off.

Steps to reproduce the bug
  1. Open RetroArch
  2. Select any overlay preset in the "On-Screen Display" tab.
  3. Switch the "Hide Overlay in Menu" option to off.
Bisect Results

This behavior was possibly always present. I encountered it the first time I tried the settings described above.

Version/Commit
  • RetroArch: 1.13.0 / ce9051f
  • Also tested on builds 1.10.0 - 1.9.0 - 1.8.0 - 1.7.0
Environment information
  • OS: Windows 10

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 on Windows 10 using RetroArch 1.13.0 with an overlay preset selected and “Hide Overlay in Menu” set to off. Trace the menu mouse handling and On-Screen Display setting interaction; done means the RetroArch mouse cursor remains active and the menu is controllable regardless of that option.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.