From: Chase Douglas <chase.douglas@canonical.com>
To: "Stéphane Chatty" <chatty@enac.fr>
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 07:44:13 -0400 [thread overview]
Message-ID: <1282045453.13264.40.camel@mini> (raw)
In-Reply-To: <D329710B-AA85-411D-834B-FE2626AD8727@enac.fr>
On Tue, 2010-08-17 at 13:33 +0200, Stéphane Chatty wrote:
> 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...
Thanks for the explanation! Since this comes down to what the user
intends with multiple touches on the screen, I'll trust your experience
over mine :).
However, while your 'eldest' method may be good for touchscreens, I
think it's a moot point for touchpads since they are relative devices
(even if they are really absolute in the driver). The user won't be able
to continuously drag across the screen by using multiple fingers because
each switch of coordinates from the eldest to the next eldest will
generate a relative motion that will just shift the object back where we
started a drag.
I'll probably leave my current implementation for the trackpad as is,
since it's easier than the 'eldest' method and provides just as much
functionality.
-- Chase
--
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
next prev parent reply other threads:[~2010-08-17 11:44 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 [this message]
2010-08-17 11:34 ` Stéphane Chatty
[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=1282045453.13264.40.camel@mini \
--to=chase.douglas@canonical.com \
--cc=chatty@enac.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).