<div class="gmail_quote">On Mon, Dec 27, 2010 at 12:18 PM, Chris Bagwell <span dir="ltr"><<a href="mailto:chris@cnpbagwell.com">chris@cnpbagwell.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sat, Dec 18, 2010 at 9:50 PM, Matt Rogers <<a href="mailto:mattr@kde.org">mattr@kde.org</a>> wrote:<br>
> On Sat, Dec 18, 2010 at 11:38 AM, Chris Bagwell <<a href="mailto:chris@cnpbagwell.com">chris@cnpbagwell.com</a>><br>
>><br>
</div><div class="im">>> Thank for detailed reply. Do you mind helping me understand how<br>
>> touchpad is being used when jumps occur? Is use case:<br>
>><br>
>> * Move cursor to area you want to click with 1 finger. Pick up 1<br>
>> finger. Click in button area with 1 finger.<br>
>><br>
>> or<br>
>><br>
>> * Move cursor to area you want to cick with 1 finger. Leave 1 finger<br>
>> on pad. Click in button area with 2nd finger.<br>
>><br>
><br>
> This is the use case that I prefer, and at least for me, the one causing the<br>
> most issues. The fact that I can't use it in this way right now drives me<br>
> nuts. :)<br>
<br>
</div>I've been thinking about this one and it looks like we will need a<br>
gesture delay in xf86-input-wacom soon. If two finger touch is<br>
detected with in X ms of initial touch then allow current 2 finger<br>
scroll logic. If its more than X ms apart (at least on clickpads)<br>
then assume its a click-and-drag and disable detection of 2 finger<br>
scroll.<br>
<br>
Can you give a little info on issue your seeing? Is it because it<br>
enters 2-finger scroll mode or is it cursor jump? If cursor jump, can<br>
you confirm your using xf86-input-synaptics 1.3.0 or later (which has<br>
something to address cursor jump for known cases)?<br>
<br></blockquote><div><br></div><div>I can't put a second finger on the touchpad without the cursor jumping around uncontrollably. That is with xf86-input-synaptics 1.3.0.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Once the delay concept is there, it also helps 1 finger use case. For<br>
clickpads, we can enable Area*Edge filtering for X ms only to debounce<br>
button clicks which then allows whole pad to still be used as long as<br>
they touch longer then X ms and no button is currently pressed.<br>
<font color="#888888"><br>
Chris<br>
</font></blockquote></div><br>