From: Guido S. <__g...@we...> - 2004-09-21 17:55:40
|
Am 21.09.2004 17:55:23 schrieb(en) Jonatan Liljedahl: > On Mon, 20 Sep 2004 20:12:01 +0100 > Tony Houghton <h...@re...> wrote: > Why does DOCK need to mean that the window should be kept on top? It > would be better if > all windows that should be kept on top need to set their > _NET_WM_STATE_ABOVE, imho. > Not many other desktop environments keep their panels/docks on top of > all other windows, do they? It's defined that way in the EWMH spec. I guess it's because EWMH is pretty much a codification of GNOME behaviour with some bones thrown to the KDE folks. > How does OroboROX 0.8.7.3 know that it shouldn't focus panel? It can't! I made it so that SKIP_PAGER/SKIP_TASKBAR implies non- focusable. But that's only hack. Might render gkrellm or other such gadgets unusuable. > > OroboROX 0.8.7.3 is one of the window managers that doesn't support > > _NET_WM_STATE_BELOW; recent 0.8.8rc* versions do I don't think more than a handfull of the dozens (hundreds?) wms out there do. > Your 0.8.7.4 seems to work well, only one question: What should > happen > when both BELOW and ABOVE gets set? Maybe BELOW should be removed if > ABOVE is set and vice versa? I would consider this an application bug. I could imagine that when you set those flags with the gtk high-level functions, it treats them as mutually exclusive. I'm too lazy to try, though. |