[PATCH] ClickPad support v4

Chris Bagwell chris at cnpbagwell.com
Mon Dec 27 10:18:46 PST 2010

On Sat, Dec 18, 2010 at 9:50 PM, Matt Rogers <mattr at kde.org> wrote:
> On Sat, Dec 18, 2010 at 11:38 AM, Chris Bagwell <chris at cnpbagwell.com>
>> Thank for detailed reply.  Do you mind helping me understand how
>> touchpad is being used when jumps occur?  Is use case:
>> * Move cursor to area you want to click with 1 finger.  Pick up 1
>> finger.  Click in button area with 1 finger.
>> or
>> * Move cursor to area you want to cick with 1 finger.  Leave 1 finger
>> on pad.  Click in button area with 2nd finger.
> This is the use case that I prefer, and at least for me, the one causing the
> most issues. The fact that I can't use it in this way right now drives me
> nuts. :)

I've been thinking about this one and it looks like we will need a
gesture delay in xf86-input-wacom soon.  If two finger touch is
detected with in X ms of initial touch then allow current 2 finger
scroll logic.  If its more than X ms apart (at least on clickpads)
then assume its a click-and-drag and disable detection of 2 finger

Can you give a little info on issue your seeing?  Is it because it
enters 2-finger scroll mode or is it cursor jump?  If cursor jump, can
you confirm your using xf86-input-synaptics 1.3.0 or later (which has
something to address cursor jump for known cases)?

Once the delay concept is there, it also helps 1 finger use case.  For
clickpads, we can enable Area*Edge filtering for X ms only to debounce
button clicks which then allows whole pad to still be used as long as
they touch longer then X ms and no button is currently pressed.


More information about the xorg-devel mailing list