Bug 304506

Summary: Maximized windows should be moved and maximized to second screen if they are moved with shortcut
Product: [Plasma] kwin Reporter: Andreas <hohenegger>
Component: coreAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED FIXED    
Severity: wishlist    
Priority: NOR    
Version: 4.8.5   
Target Milestone: 4.11   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 4.11

Description Andreas 2012-08-03 16:35:41 UTC
If I try to move a maximized window using keyboard shortcuts (move windows up/down/left/right) it is not moved at all. Instead it stays on the present screen. It would make sence to move it to the screen in the respective direction and to maximize it on this screen.

Reproducible: Always
Comment 1 Thomas Lübking 2012-08-03 17:01:36 UTC
supposingly implicitly fixed with replacing the "display borders on max'd windows" option, but could pot. be changed before as dragging a max'd window to another screen is always permitted as well.
Comment 2 Martin Flöser 2012-08-03 17:21:31 UTC
just for the record: there is a shortcut to move a window to the next screen. 
This does work for maximized windows, too
Comment 3 Thomas Lübking 2012-08-03 17:53:09 UTC
Ah, i thought he meant that one.
The "move window *" shortcuts (except for "move window") apparently do nothing here at all.
Comment 4 Thomas Lübking 2013-04-15 11:28:35 UTC
The window can now be moved, but the maximization state is not kept - needs call to checkWorkspacePosition()
Comment 5 Thomas Lübking 2013-04-28 15:54:10 UTC
Git commit 2092e203b10a951fb9ca3a8921c02e5a6b914a65 by Thomas Lübking.
Committed on 15/04/2013 at 20:43.
Pushed by luebking into branch 'master'.

validate screen and max'd state on packing windows

REVIEW: 110054
FIXED-IN: 4.11

M  +2    -0    kwin/client.h
M  +20   -9    kwin/placement.cpp

http://commits.kde.org/kde-workspace/2092e203b10a951fb9ca3a8921c02e5a6b914a65