From 5fc18091becee67964d4adce416332f04a9f6615 Mon Sep 17 00:00:00 2001
From: Dana Jansens <danakj@orodu.net>
Date: Mon, 14 Dec 2009 11:27:50 -0500
Subject: [PATCH] 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.

---
 data/rc.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/data/rc.xml b/data/rc.xml
index 8f5ee28..d7a31bd 100644
--- a/data/rc.xml
+++ b/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.
-- 
1.9.1