[PATCH 0/3] Input: synaptics - multitouch and multifinger support

[Takashi Iwai]

At Mon, 11 Oct 2010 16:24:41 +0200,
Henrik Rydberg wrote:
> 
> On 10/11/2010 04:01 PM, Takashi Iwai wrote:
> [...]
> 
> > As an example of mess of Clickpad: if you keep your finger on a button
> > area and another finger on the normal area, you shouldn't trigger the
> > multi-touch mode, no matter whether it's clicked or not.  People tend
> > to keep the finger on the button before actually dragging.
> > 
> > But, if you put both fingers in the button area and sliding together,
> > it should be handled as two-finger scrolling.  Also, if you move one
> > finger on a button area, it should be tracked as a normal pointer
> > movement.
> 
> 
> Are you aware of http://bitmath.org/code/multitouch/? The driver was developed
> to address very similar issues on the macbook trackpads.

Well, I thought Macs don't use the certain areas as virtual buttons
but determines the button by the number of fingers.  Or was it
changed?  If yes, could you point out which source file does it?

I'm looking through the git tree
http://bitmath.org/git/multitouch.git, but couldn't find out yet...

> > Another mess is that, as the default setup, the pointer movement is
> > too sensitive, and when user pushes down the touchpad for clicking,
> > the pointer moves a few or more pixels.  This eventually misses the
> > target.  So, some trick to drag the pointer is necessary for click
> > action.  One of my patches does it by introducing some "move
> > threshold" value.
> 
> 
> Also addressed in that project. What I am hoping to see, eventually, is code
> similar to the core of the multitouch project in something like ginn. This would
> exercise the whole utouch stack in an extensible way, and finally make
> multitouch trackpads work the way they are supposed to.

If the messy behavior of clickpad suits with the multi-touch library,
I have nothing against it, sure.  It was just my concern that the
clickpad-style handling might pollute the code.


thanks,

Takashi