All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Chris Bagwell <chris@cnpbagwell.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Chase Douglas <chase.douglas@canonical.com>,
	linux-input@vger.kernel.org, xorg-devel@lists.x.org,
	Andy Whitcroft <apw@canonical.com>,
	linux-kernel@vger.kernel.org,
	Peter Hutterer <peter.hutterer@who-t.net>,
	Duncan McGreggor <duncan.mcgreggor@canonical.com>
Subject: Re: [PATCH 0/3] Input: synaptics - multitouch and multifinger support
Date: Mon, 11 Oct 2010 16:49:34 +0200	[thread overview]
Message-ID: <s5hlj64g4xt.wl%tiwai@suse.de> (raw)
In-Reply-To: <4CB31E29.9020602@euromail.se>

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

  reply	other threads:[~2010-10-11 14:49 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 14:57 [PATCH 0/3] Input: synaptics - multitouch and multifinger support Chase Douglas
2010-10-08 14:57 ` [PATCH 1/3] Input: synaptics - add multitouch support Chase Douglas
2010-10-08 14:57   ` [PATCH 2/3] Input: synaptics - add multitouch multifinger support Chase Douglas
2010-10-08 14:58     ` [PATCH 3/3] Input: synaptics - remove touches over button click area Chase Douglas
2010-10-10 15:58       ` Chris Bagwell
2010-10-11 16:24       ` Chris Bagwell
2010-10-11 16:24         ` Chris Bagwell
2010-10-11 17:10         ` Takashi Iwai
2010-10-11 17:10           ` Takashi Iwai
2010-10-11 17:30           ` Dmitry Torokhov
2010-10-11 17:30             ` Dmitry Torokhov
2010-10-11 17:40             ` Takashi Iwai
2010-10-11 17:46           ` Chris Bagwell
2010-10-11 17:46             ` Chris Bagwell
2010-10-11 17:54             ` Henrik Rydberg
2010-10-11 18:29             ` Takashi Iwai
2010-10-11 18:29               ` Takashi Iwai
2010-10-10 15:44     ` [PATCH 2/3] Input: synaptics - add multitouch multifinger support Chris Bagwell
2010-10-10 15:37   ` [PATCH 1/3] Input: synaptics - add multitouch support Chris Bagwell
2010-10-10 15:41   ` Chris Bagwell
2010-10-08 16:37 ` [PATCH 0/3] Input: synaptics - multitouch and multifinger support Takashi Iwai
2010-10-08 16:38   ` Takashi Iwai
2010-10-08 17:48     ` Takashi Iwai
2010-10-08 17:15   ` Chase Douglas
2010-10-08 17:46     ` Takashi Iwai
2010-10-08 18:04     ` Dmitry Torokhov
2010-10-08 19:31       ` Takashi Iwai
2010-10-10 21:04         ` Dmitry Torokhov
2010-10-11  7:35           ` Takashi Iwai
2010-10-11  7:48             ` Henrik Rydberg
2010-10-11  7:59               ` Takashi Iwai
2010-10-11 13:41               ` Chris Bagwell
2010-10-11 13:41                 ` Chris Bagwell
2010-10-11 14:01                 ` Takashi Iwai
2010-10-11 14:01                   ` Takashi Iwai
2010-10-11 14:24                   ` Henrik Rydberg
2010-10-11 14:49                     ` Takashi Iwai [this message]
2010-10-11 15:31                       ` Henrik Rydberg
2010-10-11 15:58                         ` Takashi Iwai
2010-10-10  7:49   ` Henrik Rydberg
2010-10-10 20:59     ` Dmitry Torokhov
2010-10-11  7:28       ` Takashi Iwai
2010-10-11  7:40         ` Henrik Rydberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hlj64g4xt.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=apw@canonical.com \
    --cc=chase.douglas@canonical.com \
    --cc=chris@cnpbagwell.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=duncan.mcgreggor@canonical.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    --cc=rydberg@euromail.se \
    --cc=xorg-devel@lists.x.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.