You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With kwin's native tiling in a multi monitor setup, windows on the edge of one screen can be moved to the next screen using keyboard shortcuts.
For example, "Quick Tile right" will tile the window to the right half of the current screen, then pressing the shortcut again will move it to the left half of the monitor to the right.
Can this behavior be replicated for kzones's "Move active window..." shortcuts? I don't know if kwin scripts can read the monitor layout, but it already has shortcuts for "Move window one screen left/right/up/down", so maybe that can be reused to move the window to the appropriate monitor, then kzones can tile it to the leftmost zone if coming from the right, rightmost zone if coming from the left, and so on.
One could just use the "Move window one screen..." shortcuts directly, but this feels less streamlined due to requiring two different shortcuts.
The text was updated successfully, but these errors were encountered:
With kwin's native tiling in a multi monitor setup, windows on the edge of one screen can be moved to the next screen using keyboard shortcuts.
For example, "Quick Tile right" will tile the window to the right half of the current screen, then pressing the shortcut again will move it to the left half of the monitor to the right.
Can this behavior be replicated for kzones's "Move active window..." shortcuts? I don't know if kwin scripts can read the monitor layout, but it already has shortcuts for "Move window one screen left/right/up/down", so maybe that can be reused to move the window to the appropriate monitor, then kzones can tile it to the leftmost zone if coming from the right, rightmost zone if coming from the left, and so on.
One could just use the "Move window one screen..." shortcuts directly, but this feels less streamlined due to requiring two different shortcuts.
The text was updated successfully, but these errors were encountered: