Bug 326203

Summary: Moving maximised windows to another screen should not necessarily snap it to the MaximizeArea
Product: [Plasma] kwin Reporter: davidblunkett <dav1dblunk3tt>
Component: xrandrAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: wishlist    
Priority: NOR    
Version First Reported In: 4.10.5   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description davidblunkett 2013-10-18 14:02:10 UTC 
I have a dual screen setup and previously if I maximised a window (fills one screen) I could then drag and reposition that window where ever I want.  Lately (and I'm not sure when) if a maximised window is dragged more than 1/2 its width across the join it leaps across and maximised on the other screen which is dead annoying if I just want to reposition it. I understand the rationale behind this and for some things it is quite handy - you can nearly simply throw a window from screen to screen - but it is more annoying than useful to me and I'd like to turn it off so I can simply move the window where I want.  If I want to snap it back to the screen I'll simply maximised it again.


Reproducible: Always

Steps to Reproduce:
Drag a maximised window more than 1/2 the way across the boundary between two screens.
Actual Results:  
When more than 1/2 way it remaximised to the new screen

Expected Results:  
Nothing - you should simply be able to reposition it anywhere

I'm not using xinerama - my system is nvidiatwin view but I'm not sure if this is relevant...
Comment 1 Martin Flöser 2013-10-18 14:12:16 UTC 
just enable the quick maximization option on screen edge. When you start moving the window will unmaximize.
Comment 2 davidblunkett 2013-10-19 07:52:39 UTC 
No thanks - the maximize on a screen edge is a severely annoying option for me and Iv'e turned it off.  Basically I don't want to swap an infrequent irritation for the frequent one!
Comment 3 Martin Flöser 2016-08-29 06:31:53 UTC 
Maximization is a state. If one moves a maximized state it of course keeps the state. That's how it is implemented and optimized for the workflow of moving a maximized window. I'm sorry that this is not what you prefer, but I don't see a need to change this in general and not important enough to have a config option for it (with all the included maintenance costs).