-
-
Notifications
You must be signed in to change notification settings - Fork 849
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
Mouse clicks are far from target location at 150% display scaling #3744
Comments
Duplicate of #3733 |
This issue already exists. |
@MDSchechtman could you’re checking the behavior with 100% and 200% scaling of the screen? |
@alex-w No issue at 100% or 200% display scaling. I did find something else interesting though: initially when Stellarium opens at 150% display scaling, clicking will be accurate but only as long as the window is not resized. After resizing (or going into full screen), clicking is wildly off again and will remain so until the application is restarted. Resizing the window at 100% and 200% scaling were still fine. Updated the title. |
I can confirm the same behaviour in my Windows 10 set up:
I hope this adds any value to the bugfixer. Carsten |
@Carz10 @MDSchechtman please check version 24.4 of Stellarium |
Just a reminder I'm on a 4k monitor with 150% display scaling (or 1.5) using Arch, KDE Plasma, and Wayland. I tested the following with Stellarium 24.4: AppImage
UI widgets are scaled correctly however fonts are small, which isn't really an issue since they can be adjust in the UI. Flatpak
Disabling Wayland for the flatpak (via flatseal) fixed the mouse click behavior, which was promising. I could not get the flatpak to respect any display scaling and so it was mostly unusable. Both UI widgets and fonts were much too large. I wonder if fixing the scaling would then break mouse clicks again Native install (built from source via AUR)
Similar to the flatpak, thought I didn't tweak any environment variables. I've just been using the appImage which does work for the most part. |
WOW! Very interesting and strange results… Thanks for report! |
This may be a bug in Qt Wayland platform support. Generally, high-DPI scaling as implemented in Qt is a kludge that I aim to get rid of eventually, doing all the necessary scaling relative to the chosen font size. Much of this has already been done, except the panels and some additional quirks like line widths of the grids. Meanwhile, you can try
|
While
The above is much easier using Flatseal if anyone else is trying to replicate the workaround. This probably works for the non-flatpak version though you'll have to lookup how to disable wayland for a specific application. |
Adding to my previous comment, |
Expected Behaviour
Clicking an object, such as a star, selects that object.
Actual Behaviour
Clicking appears to be offset by a large amount, resulting in distant objects being selected when trying to select a specific target such as a star.
Steps to reproduce
Click a large bright star. Notice that it does not select, and some other star might have been selected instead.
Video: https://www.youtube.com/watch?v=JFXye0eKMHw
I assume this is related to the combination of Arch+KDE+wayland on a 4k monitor with display scaling, and if anyone has advice I would appreciate it.
System
Logfile
log.txt
The text was updated successfully, but these errors were encountered: