From: Olivier F. <fo...@xf...> - 2003-03-02 17:03:15
|
Salut Daniel, > Humm, can you tell me which WM are you running ?? Hehehe, I'm running xfwm4 (http://www.xfce.org) > > Well, all test i've made here failed with this patch (gnome/sawfish > 1.0.1/enlightenment 0.16.5, kde 3, fvwm2, windowmaker, twm ;)...) > Currently, the layer is set before window mapping otherwise WM don't > take care about (or not support that). AKAIK, neither windowmaker, twm, fvwm2 nor sawfish 1.0.x are EWMH compliant (dunno about enlightment .16) My point was about NET_WM_STATE which is an EWMH atom. EWMH prevents the app to set/unset/toggle properties (to avoid race conds between the WM and the app, which makes good sense IMO), but rather ask the WM to do the change. And the WM cannot do it if the window is not mapped simply because if it's not mapped, it's not managed and therefore the WM can't know about the window the app is talking about... I checked that by adding traces to the window manager. Actually, I was wondering why sometimes the property was applied, and sometimes not. The reason is that sometimes, the window is mapped first, sometimes not (typically, a race cond between the the app -xine in this case-, the X server and the WM)... My patch might have some side effects on older, non EWMH compliant WM, I admit I didn't check that. > > Hopes that's useful in some way (works for me at least :), > > I think it will fit in the (unhandled yet) metacity case. It should. I checked with Metacity from GNOME 2.2 and indeed it works better than before (I think) :) Cheers, -- Olivier Fourdan <fo...@xf...> http://www.xfce.org |