Re: [PATCH] hid-ntrig.c Multitouch cleanup and fix

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Rafi Rubin wrote:
> Since you're considering protocol clarification, what's your opinion on
> splitting the multi-touch and single touch (possibly emulated) to
> separate input devices?

The multi-touch protocol was designed to complement single-touch, not replace
it. The MT events were specifically designed to be ignored by current userland
applications, so there is no need to separate them into different devices.

On the contrary, the MT protocol is dependent on one of the single-touch events
BTN_TOUCH or ABS_PRESSURE to be present in the event stream for proper device
identification and for correct handling of zero-finger events. The latter
because at least one value (BTN_TOUCH or ABS_PRESSURE) must change state to pass
through input filtering when no fingers are present. This is what needs
clarification.

> Also BTN_0 or BTN_TOOL_DOUBLETAP for single touch (or both)?  It seems
> to me Wacom uses doubletap, whereas my hardware's rdesc defaults to btn0
> and evdev prefers btn0 as well.

Single touch should be goverened by one of BTN_TOUCH or ABS_PRESSURE.
BTN_TOOL_DOUBLETAP is a two-finger event.

Henrik

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

[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux