Bug 322565

Summary: decos should receive a signal on maximized border snapping and eventually manipulate their borders in return
Product: [Plasma] kwin Reporter: Martin Koller <martin>
Component: decorationsAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED FIXED    
Severity: wishlist CC: gaantonio
Priority: NOR    
Version First Reported In: 4.10.95   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: qdbus output

Description Martin Koller 2013-07-19 12:05:35 UTC
I'm testing 4.11 RC1 and see the following different behaviour to 4.10.5:

When I move a maximized window (which shows only the titlebar but no other borders),
the now moved window still has no other borders but only the titlebar, which looks wrong.
I would expect that a maximized window, when moved, is now no longer maximized and gets all the borders.

When I resize the maximized window, it now is no longer maximized and gets all its borders.

I use the QtCurve decoration, but oxygen behaves the same.

Reproducible: Always
Comment 1 Martin Flöser 2013-07-19 12:22:07 UTC
please provide output of:
qdbus org.kde.kwin /KWin supportInformation
Comment 2 Martin Koller 2013-07-22 14:42:48 UTC
Created attachment 81268 [details]
qdbus output

I'm sorry I read your comment too late - I downgraded again to 4.10.5 due to kmail2 troubles, so currently I can not provide this information.
Don't know if that still makes sense but I attach the output of current 4.10.5 installation
Comment 3 Thomas Lübking 2013-07-22 15:25:07 UTC
> electricBorderMaximize: false

the window is not unmaximized by moving it away from the top border (proof: press the maximize/restore button and you will find it at its geometry before maximization), by this the deco does not update the border.

reminds me to send hugo patches for borderchanges due to quicktiling - we could also pass snapping a maximized window the same behavior.

so far everything operates as expected.
Comment 4 Martin Flöser 2016-08-29 06:52:54 UTC
This should be fixed with kdecoration 2 which now provides information about the screen edges a window borders.