| Summary: | Cursor harder to move between screens if those are set to appear at different height relative to each-other. | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | retired <pepko94> |
| Component: | multi-screen | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.26.90 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | doodle | ||
Are you sure? I don't recall it ever working the way you say it used to work. Ah crap, I got so used to overlapping desktops that I haven't noticed workspace constraints while using mouse. Having downgraded to 5.26 I can confirm that it does indeed behave in the same way. And yeah, my panels got all messed up after downgrade. So kudos to whoever rewrote multi-display handling for 5.27. |
Created attachment 155563 [details] doodle Since 5.27 rewrite it's harder to move the cursor diagonally between screens if those are set at different height, or if one is bigger than the other. It used to be possible to move cursor smoothly between workspaces, not there's no approximation on "empty space", and so cursor hits "brick wall". Seems like a regression, is it going to be reintroduced, or is it deemed as an unnecessary complexity? Little explanation in attachments, as I'm not sure if my explanation is clear. In short, it messes with my muscle memory.