All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stéphane Chatty" <chatty@enac.fr>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Henrik Rydberg <rydberg@bitmath.org>,
	linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH RESEND] USB HID: Add ID for eGalax Multitouch used in  JooJoo tablet
Date: Tue, 17 Aug 2010 13:34:00 +0200	[thread overview]
Message-ID: <FDB1F269-49AF-4985-BD0F-869D23833D2B@enac.fr> (raw)
In-Reply-To: <1282042502.13264.21.camel@mini>


Le 17 août 10 à 12:55, Chase Douglas a écrit :

> On Tue, 2010-08-17 at 09:49 +0200, Stéphane Chatty wrote:
>> Le 16 août 10 à 17:30, Henrik Rydberg a écrit :
>>
>>   - the single touch emulation is highly device dependent. I was (and
>> still am) pretty proud of my choice of tracking the 'oldest' finger
>> on the panel: this turns multitouch panels into single touch panels
>> that are impervious to parasite touches. But the drawback is that
>> currently there is no generic method for this tracking: I used
>> whatever device-specific information I could use (order of fingers in
>> a message, tracking id, etc).
>
> Stéphan,
>
> Can you explain in more detail why you chose an 'oldest' finger  
> approach
> for single touch emulation? I wonder if it's the best mechanism. Take
> the following example:
>
> 1. User touches with one finger and intends to drag an object on  
> screen
> 2. User touches another finger down, either accidentally or
> intentionally, while dragging the first finger
> 3. User releases first finger to end the drag
> 4. Object suddenly is dragged under the second finger
>
> As I'm implementing support for the Magic Trackpad right now, I'm  
> having
> to figure out the best way to do single-touch emulation. What I'm
> currently doing is converting the first finger touched for single- 
> touch
> emulation, and when that finger is released no single-touch emulation
> can occur until all fingers have left the screen again.

Yes, the debate is what to do when the 'actual oldest' finger is  
released: should the 'second oldest' take its place or should this be  
a release or should somthing else occur.

Some arguments in favour of the first option:
- My experience is that 'accidental' touches are transient.  
Therefore, the conjunction of having an accidental touch and a  
release is not very frequent.
  - At the opposite, on very large screens, it may sometimes be  
comfortable to "replace one finger with another", thus 'moving' the  
dragged object from one hand to the other.

More or less, the debate is about statistics and user experience  
design...

Cheers,

St.

--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-08-17 11:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16 15:30 [PATCH RESEND] USB HID: Add ID for eGalax Multitouch used in JooJoo tablet Henrik Rydberg
2010-08-17  7:49 ` Stéphane Chatty
2010-08-17  9:56   ` Henrik Rydberg
2010-08-19 21:45     ` Stéphane Chatty
2010-08-19 21:59       ` Henrik Rydberg
2010-08-17 10:55   ` Chase Douglas
2010-08-17 11:33     ` Stéphane Chatty
2010-08-17 11:44       ` Chase Douglas
2010-08-17 11:34     ` Stéphane Chatty [this message]
     [not found] <m339wl2ug6.fsf@pullcord.laptop.org>
2010-08-12 23:10 ` Chris Ball
     [not found]   ` <m3hbiz8m11.fsf-0VGQAjvlmrQzNDMTQreKSUB+6BGkLq7r@public.gmane.org>
2010-08-12 23:15     ` Jiri Kosina
2010-08-13 10:47       ` Stéphane Chatty
2010-08-14  2:33         ` Chris Ball
2010-08-16 14:03           ` Jiri Kosina
2010-08-16 13:58         ` Jiri Kosina
2010-08-16 15:17           ` Stéphane Chatty
2010-08-16 15:37             ` Stéphane Chatty
     [not found]             ` <F35B802E-C47A-47BF-A350-8F57250D4394-rXV5z7KbLFk@public.gmane.org>
2010-08-18  9:33               ` Mathieu Virbel

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=FDB1F269-49AF-4985-BD0F-869D23833D2B@enac.fr \
    --to=chatty@enac.fr \
    --cc=chase.douglas@canonical.com \
    --cc=linux-input@vger.kernel.org \
    --cc=rydberg@bitmath.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.