Large changes for xfce4 in CVS
Olivier Fourdan
fourdan at xfce.org
Thu Dec 12 22:35:29 CET 2002
Hi Jasper,
This was because of a variable not initialized in xfwm4.
Should be fixed in CVS now.
Cheers,
Olivier.
On Thu, 2002-12-12 at 12:17, Jasper Huijsmans wrote:
> Olivier,
>
> On Thu, 12 Dec 2002 11:06:37 +0100
> Jasper Huijsmans <jasper at moongroup.com> wrote:
> ...
> > o Panel now can be on three 'layers': On top, normal, and on bottom.
> > (I just notice 'normal' doesn't work yet)
> >
> I now get this:
> [~/cvs/xfce-devel/xfce4/panel]$ xprop | egrep -e "LAYER|_WM_STATE"
> _WIN_LAYER(CARDINAL) = 2
> _NET_WM_STATE(ATOM) = _NET_WM_STATE_STICKY, _NET_WM_STATE_BELOW
>
> [~/cvs/xfce-devel/xfce4/panel]$ xprop | egrep -e "LAYER|_WM_STATE"
> _WIN_LAYER(CARDINAL) = 53
> _NET_WM_STATE(ATOM) = _NET_WM_STATE_STICKY
>
> [~/cvs/xfce-devel/xfce4/panel]$ xprop | egrep -e "LAYER|_WM_STATE"
> _WIN_LAYER(CARDINAL) = 12
> _NET_WM_STATE(ATOM) = _NET_WM_STATE_STICKY, _NET_WM_STATE_ABOVE
>
> Note how the layer in normal mode is set to 53. Is this a xfwm4 bug or
> am I doing something wrong?
>
> hmm, it seems this layer is rather random and is only present when
> previously set by changing to _WM_STATE_ABOVE/BELOW. Should I delete
> this property myself?
>
>
> Jasper
--
Olivier Fourdan <fourdan at xfce.org>
http://www.xfce.org
More information about the Xfce4-dev
mailing list