Dan Espen wrote: > Michael Großer <michael.gros...@gmx.de> writes: > >> Our conversation drifted into a direction where I stated that >> I didn't understand the difference between "res_class" and >> "res_name". >> >> You answered that only programmers are supposed to understand >> the documentation related to "res_class" and "res_name", and that >> I should concentrate on something more useful. > > I must have missed this conversation.
http://www.mail-archive.com/fvwm@fvwm.org/msg01425.html > res_class and res_name are explained in the ICCCM. Thanks! The pieces result into a puzzle that I now begin to understand slowly: http://tronche.com/gui/x/icccm/ http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.2.1 http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.2.5 http://www.jumping-blue-turtle.com/fvwm/will_disappear_on_2012-04-04/name_and_class.png > For our purposes, they are just 2 of the fields Fvwm uses > for style matching. Both can be displayed for any window > by FvwmIdent. > I recommend to recheck this piece of documentation: +---------------------+----------------------------+ |res_class | | | | Runs when the WM_CLASS | | | property of a window | | | changes. | +---------------------+----------------------------+ |res_name | | | | Runs when the WM_CLASS | | | property of a window | | | changes (for the | | | resource). | +---------------------+----------------------------+ Since the ICCCM standard clearly contains both a WM_CLASS property and a WM_NAME property, the man-page reader could think that there is an error when WM_CLASS runs "res_class" and WM_CLASS runs "res_name". The man-page should explain why not WM_NAME does run "res_name". Why WM_CLASS? Or is there an error? Consider this action as a kind of quality management ;-) Michael
<<inline: name_and_class.png>>
