4fd2af39a5432eaad03af6a48cd16988a165fbbb split out the touch setting from a combined property into it's own separate one. The index didn't get updated though, which means wcmTouch was assigned random garbage.
Signed-off-by: Peter Hutterer <[email protected]> --- Ping, I think this might be the touch property weirdness you're seeing on resume. src/wcmXCommand.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/wcmXCommand.c b/src/wcmXCommand.c index 698c280..31b9945 100644 --- a/src/wcmXCommand.c +++ b/src/wcmXCommand.c @@ -552,8 +552,8 @@ int xf86WcmSetProperty(DeviceIntPtr dev, Atom property, XIPropertyValuePtr prop, if ((values[0] != 0) && (values[0] != 1)) return BadValue; - if (!checkonly && common->wcmTouch != values[1]) - common->wcmTouch = values[1]; + if (!checkonly && common->wcmTouch != values[0]) + common->wcmTouch = values[0]; } else if (property == prop_hover) { CARD8 *values = (CARD8*)prop->data; -- 1.6.5.2 ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
