https://bugs.kde.org/show_bug.cgi?id=465937
Roy Orbitson <roy-orbit...@devo.net.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |roy-orbit...@devo.net.au
--- Comment #37 from Roy Orbitson <roy-orbit...@devo.net.au> ---
For a solution, instead of a single, mutable split stop, could it remember
however many stops as have been created by resizing, plus an immutable 50/50
stop, so that Meta + Arrow keys could cycle through those before moving to
opposite edges and adjacent screens? The resizing of adjacent windows could
also be limited to only the last most recently used windows that are snapped to
both an opposite edge/corner and the shared edge of the window being resized.
Windows behind those would remain untouched but could, of course, be snapped to
the new stop by the user. Unused stops would need to be garbage collected,
otherwise there would still be the reported memory effect and the possible
stops would grow out of control.
For getting around the current problem, I found an accurate way to reset to
50/50 is to use KRuler:
1. snap it to a side
2. press D to change direction if 0 is not at the screen's edge
3. resize it to half your monitor resolution
4. hover your mouse over the last pixel to check its exact length
5. repeat steps 3 & 4 until it's correct
It's quite a frustrating UX.
--
You are receiving this mail because:
You are watching all bug changes.
