WM attributes: windowmaker vs gaim

wwp <[email protected]>
Newsgroups gmane.compw.window-managers.windowmaker.user
Message-ID <[email protected]>
Hello dear windowmaker users,


I'm fighting w/ wmaker 0.80.2 (back from 0.9x.x) and gaim 1.1.x to set
different WM attributes to all gaim window, and failing in fact. All gaim
windows appear to be named "gaim.Gaim". According to the FAQ excerpts below,
gaim developers says that they do things in a correct way and that the window
manager would have to manage the WM_WINDOW_ROLE.

So who is right or wrong? And is there a way to set different WM attributes to
gaim windows in fact? Is that a holy war :-)? Any hint?


http://gaim.sourceforge.net/faq.php#q24

Q: Why does Gaim use the same WM_CLASS for every window? It makes it
impossible to control window size and placement for the buddy list separately
from the conversations.

A:  Both strings in the WM_CLASS property are supposed to be the same for all
windows in the same instance of an application. ICCCM states that one is meant
to be the same for all instances of the application, the other is meant to be
unique to that instance of the application. ICCCM also states "If a client has
multiple windows with identical WM_CLASS and WM_NAME properties, then it
should provide a WM_WINDOW_ROLE property."

    Gtk+ sets these WM_CLASS values for us so that they are unique for Gaim
instances, and the documentation for the gtk_window_set_wmclass function says
explicitly not to use it for anything else. Gaim uses the WM_WINDOW_ROLE hint
to differentiate windows. If your window manager is having problems
differentiating between Gaim windows, please ensure that it uses the
WM_WINDOW_ROLE hint per the ICCCM


Regards,

-- 
wwp
_______________________________________________
INFO: https://windowmaker.org/lists/listinfo/wm-user
ARCHIVE: https://windowmaker.org/lists/archive/wm-user/
FAQ: http://windowmaker.org/faq.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.