Re: [PATCH v2] input: mt: Interface and MT_TOOL documentation updates

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Chase Douglas
Date: Monday, December 13, 2010 - 10:46 am

On 12/10/2010 09:24 AM, Henrik Rydberg wrote:

By definition, this only covers rectangles with two coordinates to
define the shape and location. Why do we want to call it envelope? It's
just extra confusion to me. Why not call it MT_TOOL_RECT?

Please describe how to use this tool type. Its usage is different than
any tool type usage before, so an explanation would be helpful. Must the
value of the tool on the first touch be 0 until a second touch can
define the rect? Or, can touches always default the value to 1 since
we're talking about devices that only support two fingers?

If this is really to remedy only poor two finger devices, would it be
better to flag the device itself somehow to say "don't trust this
device's coordinate positions" (or something more elegant)? This would
prevent an extrapolation of tool types to multiple fingers at a time.

Lastly, using tool types for this seems odd since this does not signify
a physical tool. It merely signifies that the device coordinates cannot
be trusted literally. Maybe we should use some other namespace for
binding information across multiple touches, like MT_BIND_RECT?

-- Chase
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH v2] input: mt: Interface and MT_TOOL documentat ..., Chase Douglas, (Mon Dec 13, 10:46 am)