On Mon, Oct 10, 2011 at 1:43 PM, Thomas Jaeger <thjae...@gmail.com> wrote: > I do have a patch for you, though: There is no reason to do > any gesture processing if gestures are disabled (this can cause > unexpected fallout when modifying the non-gesture codepath). >
I do not see why your latest patch would be needed. The "ret:" block already contains an if() so that single finger taps are ignored when gestures are disabled. So that part is already covered. Single Finger presses (length longer than max tap) are still processed when gestures are disabled but the reason for that is touchscreens users generally do not consider the left-click-on-touch as a gesture. Its a minimum requirement of a touchscreen driver. I'm thinking a more useful feature is to expose a new property were user can define what button taps send; and a button of 0 means do not send as a way of turning off individual gesture. xf86-input-synaptics support this with their ClickFinger* option. So for your use case, you could then set single tap to button 0 to disable it and double tap to button 1. Chris ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
