Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor bug: Clicking on taskbar buttons requires precision at certain scale values (see workaround) #786

Open
homandr opened this issue Apr 3, 2024 · 1 comment

Comments

@homandr
Copy link

homandr commented Apr 3, 2024

I have been using RetroBar for a few weeks now, and from the start there was one very annoying issue that I felt immediately. When clicking on the toolbar buttons or Start button, the mouse cursor has to be quite precisely on the button. If you move the cursor all the way down to the bottom of the screen, as far as it can go to the point where it's not even seen and technically not within the button area, and then click, nothing happens. The click doesn't register on the button. This is not the case for native Windows taskbar. I do have somewhat non-standard setup - 4K resolution (3840x2160) with 200% OS scaling. Not sure if it's reproducible for other configurations.

It seemed like a minor issue that I could get used to, however, it turned out to be more annoying than I had anticipated. Decades of motor memory are hard to beat. Taskbar is arguably the most important part of functional UI, especially for users with many windows and a lot of things going on. On a busy day it gets hundreds, if not thousands of clicks per day (Alt+Tab doesn't always help). Bottom line, I wasn't satisfied and was going to open a bug report. First, I validated that historical XP behaviour was correct. Then I started to fiddle with RetroBar settings and to my great relief, I found a workaround. I'm posting this bug report mainly for anyone else running into this issue, but if it's something easy enough to fix, that would be nice.

Workaround:
First of all, any non-classic theme works correctly.
Second, by trial and error I figured out this issue affects only certain scale levels. It was a pure coincidence that the level I settled for in the beginning was impacted. These levels work correctly: 100, 115, 120, 125, 140, 145, 150, 160, 165, 170, 175, 190, 195, 200. The rest do not.

@Nxkorasu
Copy link

Nxkorasu commented Apr 8, 2024

Program seems to have issues with Windows´ Upscaling (#735)
Pretty sure if you try using normal scaling (tho everything will look small) the issue dissapears

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants