| commit | 7d6ecb51f66b65221a5df56f2e4907f7a65f4ee4 | |
| author | Christophe CURIS <christophe.curis@free.fr> | |
| Mon, 15 Dec 2014 22:22:21 +0000 (15 23:22 +0100) | ||
| committer | Carlos R. Mafra <crmafra@gmail.com> | |
| Tue, 16 Dec 2014 09:37:48 +0000 (16 09:37 +0000) | ||
| tree | 2fa4949b266f61d4d5693576cc518c78c4b076cd | treesnapshot (tar.gz zip) |
| parent | be1c2a01dc8af1fcef6bf1b80c5a4038603d24b7 | commitdiff |
wmaker: rewrote the update of _NET_WORKAREA property
As reported by Moritz, the Qt toolkit (and maybe a few other ones) are
using the content of this property, but WindowMaker did not set it properly
so for examples the menus in KDE could fail to display in multi-screen
configuration (probably because the toolkit is using the property to make
sure the menu stays in the visible area).
The original code just assumed it was safe to use the usable area of the
1st screen in the list, but unfortunately it is not that simple.
The new code calculates a rectangle that contains the usable region from
all the screens, so the toolkit gets a more accurate value.
Signed-off-by: Christophe CURIS <christophe.curis@free.fr>
As reported by Moritz, the Qt toolkit (and maybe a few other ones) are
using the content of this property, but WindowMaker did not set it properly
so for examples the menus in KDE could fail to display in multi-screen
configuration (probably because the toolkit is using the property to make
sure the menu stays in the visible area).
The original code just assumed it was safe to use the usable area of the
1st screen in the list, but unfortunately it is not that simple.
The new code calculates a rectangle that contains the usable region from
all the screens, so the toolkit gets a more accurate value.
Signed-off-by: Christophe CURIS <christophe.curis@free.fr>
| src/wmspec.c | diffblobblamehistory |