From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Rafi Rubin <rafi@seas.upenn.edu>
Cc: linux-input@vger.kernel.org, Ping <pinglinux@gmail.com>
Subject: Re: RFC: touch event clarification
Date: Tue, 20 Apr 2010 23:23:50 -0700 [thread overview]
Message-ID: <20100421062350.GG4364@core.coreip.homeip.net> (raw)
In-Reply-To: <4BCC1792.1020901@seas.upenn.edu>
Hi Rafi,
> Dmitry: would you care to clarify the meaning of the basic touch events? It
> might also be helpful to add more comments to input.h or add something to the
> Documents directory.
>
>
> My current understanding:
> BTN_TOOL_FINGER: touch pad single finger
Correct.
> BTN_TOOL_(DOUBLE|TRIPLE|QUAD)TAP: touch pad 2,3 and 4 fingers
Tapping with more than one finger, These events are tailored to
touchpads that can only report numberf or contacts but not discrete
coordinates for every contact,
> BTN_TOUCH: touch screen single finger
Right.
> BTN_[0-N]: not really for fingers.
>
Right, these are miscellaneous buttons.
>
> Are the taps at all appropriate for touch screens?
I do not think tap makes sense for touchscreens, the act of touching
should cause "select" or "action" event. Unlike other devices with
touchscreens you do not need to track movement of a pointer, your finger
ios a pointer and when you touch you mena to perform an action. At least
this is the model I'd operate with.
> How should the wacom
> non-screen tablets be treated, should they act like touch pads both for absolute
> and relative modes?
Yes, since they are physically separate from treh screem tracking
pointer makes sense for tablets.
> Should there be any difference between pad and screen devices with respect to
> multitouch events (currently, I'm assuming not)?
>
Umm... if you are referring to gestures then I think they should exibit
similar behavior.
--
Dmitry
prev parent reply other threads:[~2010-04-21 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 8:42 RFC: touch event clarification Rafi Rubin
2010-04-21 6:23 ` Dmitry Torokhov [this message]
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=20100421062350.GG4364@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=pinglinux@gmail.com \
--cc=rafi@seas.upenn.edu \
/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).