[PATCH] ClickPad support v4
yan.i.li at intel.com
Tue Dec 28 18:54:47 PST 2010
On Tue, 2010-12-28 at 02:18 +0800, Chris Bagwell wrote:
> On Sat, Dec 18, 2010 at 9:50 PM, Matt Rogers <mattr at kde.org> wrote:
> > 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
Sorry, why wacom? Shouldn't it be xf86-input-synaptics?
> 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)?
I have tested a vanilla xf86-input-synaptics 1.3.0 driver and it doesn't
prevent the jumpy issue because this ClickPad used in Lenovo IdeaPad
S10-3t doesn't support detecting of 2-finger nor finger width. So I
suspect the touchpad just sends out X/Y of either 1st or 2nd finger
randomly, thus caused the jumpy cursor.
I'll try to catch the event by using evtest later. But the symptom is
just like you put two fingers onto any touchpad that can't support
2-finger nor finger width.
> 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.
MeeGo Team, Opensource Technology Center, SSG, Intel
Office tel.: +86-10-5751-1695 (inet: 8-751-1695)
OpenPGP key: 5C6C31EF
IRC: yanli on network irc.freenode.net
More information about the xorg-devel