In the applications section tell the user to use _OB_* properties for the name/class/role, and refer to the still-non-existant obprop tool.
Dana Jansens danakj@orodu.net
1 files changed,
5 insertions(+),
5 deletions(-)
jump to
M
data/rc.xml
→
data/rc.xml
@@ -646,11 +646,11 @@ <!--
# this is an example with comments through out. use these to make your # own rules, but without the comments of course. - <application name="first element of window's WM_CLASS property (see xprop)" - class="second element of window's WM_CLASS property (see xprop)" - role="the window's WM_WINDOW_ROLE property (see xprop)" - type="the window's _NET_WM_WINDOW_TYPE (if unspecified, then - it is dialog for child windows)"> + <application name="the window's _OB_NAME property (see obprop)" + class="the window's _OB_CLASS property (see obprop)" + role="the window's _OB_ROLE property (see obprop)" + type="the window's _NET_WM_WINDOW_TYPE (see obprob).. + (if unspecified, then it is 'dialog' for child windows)"> # the name or the class can be set, or both. this is used to match # windows when they appear. role can optionally be set as well, to # further restrict your matches.