added 'SetXProp' action and (@PROP=foo) clientpattern

these two allow 'tagging' of arbitrary windows with 'tags' (or 'labels'). such 'tagged' windows can then be used in ':NextWindow (@PROP=foo)' commands to quickly cycle through a subset of available windows.
since the 'tags' are applied as real xproperties to a window they survive a restart of fluxbox or even another windowmanager. the user can also set the tags by using xprop(1).

the next step regarding the UI should be to visualize the tags of a window.

1 files changed, 5 insertions, 2 deletions

diff --git a/src/ClientPattern.hh b/src/ClientPattern.hh
index 6aa2e11..315edb1 100644
--- a/src/ClientPattern.hh
+++ b/src/ClientPattern.hh
@@ -54,7 +54,8 @@ public:
     enum WinProperty {
         TITLE = 0, CLASS, NAME, ROLE, TRANSIENT,
         MAXIMIZED, MINIMIZED, SHADED, STUCK, FOCUSHIDDEN, ICONHIDDEN,
-        WORKSPACE, WORKSPACENAME, HEAD, LAYER, URGENT, SCREEN
+        WORKSPACE, WORKSPACENAME, HEAD, LAYER, URGENT, SCREEN,
+        XPROP
     };
 
     /// Does this client match this pattern?
@@ -70,9 +71,11 @@ public:
      * Add an expression to match against
      * @param str is a regular expression
      * @param prop is the member function that we wish to match against
+     * @param negate is if the term should be negated
+     * @param xprop is the name of the prop if prop is XPROP
      * @return false if the regexp wasn't valid
      */
-    bool addTerm(const FbTk::FbString &str, WinProperty prop, bool negate = false);
+    bool addTerm(const FbTk::FbString &str, WinProperty prop, bool negate = false, const FbTk::FbString& xprop = FbTk::FbString());
 
     void addMatch() { ++m_nummatches; }
     void removeMatch() { --m_nummatches; }