Running "xsetwacom get" on a button which contain a "modetoggle" or
"displaytoggle" action will result in output which cannot be parsed
by "xsetwacom set". Both of these actions are treated like buttons,
printing extra data that is not expected by the "set" command.

Signed-off-by: Jason Gerecke <jason.gere...@wacom.com>
---
 tools/xsetwacom.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/xsetwacom.c b/tools/xsetwacom.c
index 95f7a6c..cf43fe7 100644
--- a/tools/xsetwacom.c
+++ b/tools/xsetwacom.c
@@ -2022,7 +2022,7 @@ static int get_actions(Display *dpy, XDevice *dev,
                if (current_type == AC_KEY)
                        sprintf(str, "%c%s ", press_str,
                                XKeysymToString(detail));
-               else
+               else if (current_type == AC_BUTTON)
                        sprintf(str, "%c%d ", press_str, detail);
                strcat(buff, str);
                last_type = current_type;
-- 
2.7.0


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to