scroll wheel “catching” on menu elements
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Hi!
(Windows 10 64-bit, RetroArch v1.9.0)
This is a peeve of mine with several pieces of software:
I'm in View > Settings > Saving in the desktop menu.
I'm scrolling down with the hyper-scroll feature on my Logitech mouse,
and during the scroll, the mouse cursor touches the SaveRAM Autosave Interval: as the page moves underneath it,
and within a split second, it's highlighted that setting's input field, and dragged the number all the way down to 0,
because I was scrolling downwards (really fast) when the cursor accidentally hovered over it.
If a menu page is even close to being large enough to require a scroll down,
then nothing on that page should be touchable by scroll wheel,
and then for consistency's sake, nothing on any page.
At the very least you should have to click on it first. It makes me scared to use my scroll wheel.
Thanks.
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
No source file or test is named. First reproduce the behavior in View > Settings > Saving with a fast scroll wheel, then trace the desktop menu input handling. Done means scrolling over a setting no longer changes or focuses its value unless the control has been explicitly clicked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100