linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* RFC: touch event clarification
@ 2010-04-19  8:42 Rafi Rubin
  2010-04-21  6:23 ` Dmitry Torokhov
  0 siblings, 1 reply; 2+ messages in thread
From: Rafi Rubin @ 2010-04-19  8:42 UTC (permalink / raw)
  To: linux-input, Dmitry Torokhov; +Cc: Ping, Rafi Rubin

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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
BTN_TOOL_(DOUBLE|TRIPLE|QUAD)TAP: touch pad 2,3 and 4 fingers
BTN_TOUCH: touch screen single finger
BTN_[0-N]: not really for fingers.


Are the taps at all appropriate for touch screens?  How should the wacom
non-screen tablets be treated, should they act like touch pads both for absolute
and relative modes?

Should there be any difference between pad and screen devices with respect to
multitouch events (currently, I'm assuming not)?


Thanks,
Rafi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvMF48ACgkQwuRiAT9o60/5+ACg+JjfmgxYWNymySwDI9uTStaN
XrEAn2B/ZiP5j6BZyQ7IvgIg1hc16IRh
=928b
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RFC: touch event clarification
  2010-04-19  8:42 RFC: touch event clarification Rafi Rubin
@ 2010-04-21  6:23 ` Dmitry Torokhov
  0 siblings, 0 replies; 2+ messages in thread
From: Dmitry Torokhov @ 2010-04-21  6:23 UTC (permalink / raw)
  To: Rafi Rubin; +Cc: linux-input, Ping

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-04-21  6:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-19  8:42 RFC: touch event clarification Rafi Rubin
2010-04-21  6:23 ` Dmitry Torokhov

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).