https://bugs.kde.org/show_bug.cgi?id=489136
--- Comment #9 from qlum <qlum...@gmail.com> --- (In reply to Nate Graham from comment #7) > Ah, if it's just about diagonals, that may be a legit issue if you've got > your screens configured so that they really are diagonal to each other. Can > you attach a screenshot that shows your screen layout on System Settings > Display & Monitors page? Not at all just a factor in making it feel inconsistent for it's intended use. Just to sum up my personal core issue: My intended usecase for this feature is to use the edge barrier as some sort of virtual space between my screens. The current speed dependent implementation is not useful for this use-case. The reason I want this is to offer mouse movements that map more directly to what I see. If I move my mouse 1cm that corrsponds to a 15cm movement of my cursor in my current setup, however if I cross a 3cm space between screens that 15cm will visually overshoot. If there was a screen barrier that was a fixed number in px, independent of movement speed, I could set it to roughly 280px and create movements that better map to the real world movement of the cursor, while at the same time offering a buffer zone for window snapping. A setting to change / disable the velocity component would make this a useful feature for me, as it stands now it's detremental. So I guess it's a minor feature request. -- You are receiving this mail because: You are watching all bug changes.
