Bug 182625 - Panel on dual monitor does not prevent windows from maximizing if the panel is on the side where the monitors "connect"
Summary: Panel on dual monitor does not prevent windows from maximizing if the panel i...
Status: RESOLVED DUPLICATE of bug 94470
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-31 20:37 UTC by Pascal Bakhuis
Modified: 2013-03-24 12:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Dual monitor panel, window full screen issue (457.74 KB, image/jpeg)
2009-01-31 20:41 UTC, Pascal Bakhuis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Bakhuis 2009-01-31 20:37:52 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

I'll try to describe this as simple as possible

I've 2 monitor next to eachother. If I put a panel on the left side of the right monitor and then maximize a window on the right screen, it will display a part under the panel.
It does work fine if I put the panel on the right side of the right screen.

Strangely enough, putting the panel on the right side of the left monitor and maximizing a window on it does work properly. I'll post a screenshot of the problem.
Comment 1 Pascal Bakhuis 2009-01-31 20:41:33 UTC
Created attachment 30795 [details]
Dual monitor panel, window full screen issue

The promised screenshot.
With eclipse maximised / being partially covered by the panel on the left.
Comment 2 Aaron J. Seigo 2009-05-09 02:08:32 UTC
this is a problem with netwm extended struts and how the window manager handles them. we don't register keep-the-window-out-of-this-area struts if it isn't on an edge of the combined desktop rect.
Comment 3 Martin Flöser 2009-07-02 10:36:38 UTC

*** This bug has been marked as a duplicate of bug 167852 ***
Comment 4 Dotan Cohen 2013-03-24 12:11:41 UTC

*** This bug has been marked as a duplicate of bug 94470 ***