Bug 473785

Summary: Feature request: more intuitive screen transitions
Product: [Plasma] kwin Reporter: mashkal2000 <mashkal2000>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: nate
Priority: NOR    
Version: 5.27.6   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: mouse gets stuck at corners
not stuck

Description mashkal2000@gmail.com 2023-08-26 22:30:39 UTC
Created attachment 161203 [details]
mouse gets stuck at corners

SUMMARY
Feature request: more intuitive screen transitions

I have monitors with nearly the same physical size, but different resolutions. When I move the mouse from 1 monitor to the other, the mouse often gets stuck on the corners of the larger monitor. See the attachment. I'd like the mouse to transition between monitors in a way that when the 2 screens are adjacent, every pixel along that edge of the first monitor corresponds to some pixel on the edge of the other monitor. See the 2nd attachment. Then the mouse wouldn't get stuck.
Comment 1 mashkal2000@gmail.com 2023-08-26 22:31:23 UTC
Created attachment 161204 [details]
not stuck

Mouse would move between the monitors regardless of the position along that edge
Comment 2 mashkal2000@gmail.com 2023-08-26 22:32:23 UTC
(In reply to mashkal2000@gmail.com from comment #1)
> Created attachment 161204 [details]
> not stuck
> 
> Mouse would move between the monitors regardless of the position along that
> edge

To be clear this is not a suggestion for the UI of the screen configuration tool - that's fine as is. The attachment is just a diagram to show the behaviour I want as a user.
Comment 3 Nate Graham 2023-08-28 20:12:24 UTC
Thanks for the idea, but getting stuck is sort of intentional in the current design. Screen positioning and cursor mapping are incredibly complex due to the diversity of screen combinations and how we let you arbitrarily move and position them relative to one another. So I'm afraid the requested feature is not feasible to implement, sorry!