| Summary: | Snapping makes it impossible to set up the positioning perfectly on a multi screen setup in the KCM | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Claudius Ellsel <claudius.ellsel> |
| Component: | kcm_kscreen | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | nate, nicolas.fella, plasma-bugs-null, steve |
| Priority: | NOR | Keywords: | multiscreen, usability |
| Version First Reported In: | 5.19.0 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot showing the setup | ||
|
Description
Claudius Ellsel
2020-08-25 19:33:02 UTC
What does "perfectly" mean to you? Created attachment 131201 [details]
Screenshot showing the setup
I attached a screenshot. Notice the mouse cursor. On the real screen there is a slight jump from one screen to another. Today that seems to look good. Yesterday however (I think on Wayland), I did not manage to make the jump unnoticeable, since I could not position the monitor positions precisely enough, because they would always snap near the perfect position. Instead it was something around some centimeters and a bit annoying.
Some time ago I noticed the problem is in fact a bit more complicated. This issue might still exist, but my problem is overlapped with a different one. Unfortunately it took me some time to get back to this report to note that. Probably due to different screen densities, there is one sweet spot on the vertical line where both screens meet each other where the mouse cursor doesn't jump when moving it over (its size changes slightly, though but that is a different problem, probably). Above that sweet spot or below, the cursor will always jump up or down. Do you know a good place where to discuss fixes for that behavior? I assume one has to somehow adjust the scaling of both monitors, so they match each other? Maybe that could even be done automatically (possibly by the systemsettings KCM) if one can get the pixel density of all monitors. As written above, if I had monitors with the same pixel density, I think the snapping could cause a problem when the sweet spot of no jumping cursor couldn't be set up due to it. Hi.. Just to say this issue still exists (Plasma 5.25, Wayland). The snapping does seem to be related to the screen scales, but it ends up hindering more than helping. I have three screens, set to 145%, 170% and 100%. The first two are the laptop and an external monitor that physically align at the bottom. The snapping in the system settings stops them from being alignable at their lower edges. It would allow aligning them at the top, but who has a laptop physically aligned with an external monitor at the top? The problem wasn't really visible under X11 as all screens had the same scale; it was also possible to use xrandr to do stuff the system settings couldn't. A checkbox in the system settings to disable snapping would be great. A CLI program with a subset of xrandr functionality for Wayland (ie: positioning) would also be a usable workaround. Does one exist already? Lastly, even hand-editing an rc-file and killing+restarting plasmashell or some other process would do, I think. Perhaps somebody could tell me which file and which process - I wasn't able to find out. Thanks... *** This bug has been marked as a duplicate of bug 355119 *** |