Is XMonad intended to respect _NET_WM_WINDOW_TYPE_DOCK? I note that when I start applications like kicker, gkrellm, etc., (which xprop says have _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK) they sort of get managed (xmonad gives them a suitable managed window, though often it's blank (because the application's drawn itself elsewhere)). Shouldn't xmonad just ignore such client windows?
xmonad:
Is XMonad intended to respect _NET_WM_WINDOW_TYPE_DOCK? I note that when I start applications like kicker, gkrellm, etc., (which xprop says have _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK) they sort of get managed (xmonad gives them a suitable managed window, though often it's blank (because the application's drawn itself elsewhere)). Shouldn't xmonad just ignore such client windows?
Hmm, perhaps. I'd have to read the spec. We haven't looked at this yet. On the todo list. -- Don
On Fri, 01 Jun 2007 19:10:16 +0100
Bruce Stephens
Is XMonad intended to respect _NET_WM_WINDOW_TYPE_DOCK? I note that when I start applications like kicker, gkrellm, etc., (which xprop says have _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK) they sort of get managed (xmonad gives them a suitable managed window, though often it's blank (because the application's drawn itself elsewhere)). Shouldn't xmonad just ignore such client windows?
xmonad is intentionally ignorant of EWMH hints like _NET_WM_WINDOW_TYPE_DOCK at the moment. We're considering using the _NET_WM_STRUT property to automatically manage windows as statusbars. Stay tuned for more info. Cheers, Spencer Janssen
participants (3)
-
Bruce Stephens -
dons＠cse.unsw.edu.au -
Spencer Janssen