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.
This commit is contained in:
parent
9ba2b04e96
commit
5fc18091be
1 changed files with 5 additions and 5 deletions
10
data/rc.xml
10
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.
|
||||
|
|
Loading…
Reference in a new issue