lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CFFC3C2.1080905@canonical.com>
Date:	Wed, 08 Dec 2010 09:43:30 -0800
From:	Chase Douglas <chase.douglas@...onical.com>
To:	Henrik Rydberg <rydberg@...omail.se>
CC:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jiri Kosina <jkosina@...e.cz>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] input: mt: Add an envelope tool type

On 12/07/2010 03:29 AM, Henrik Rydberg wrote:
> Some touch devices are capable of detecting the envelope or hull
> of the touches, but not the touches themselves. This patch adds
> the MT_TOOL_ENVELOPE touch type to be used for such devices.
> 
> Signed-off-by: Henrik Rydberg <rydberg@...omail.se>
> ---
> Hi all,
> 
> This patch represents an MT solution for those devices that can detect
> and report some effects of dual touch, but cannot report individual
> contacts. Synaptics and elantech are two examples. Having the drivers
> report the bounding rectangle of the touches is useful in userland,
> since the information makes it possible to implement zooming
> gestures. At the same time, it would be confusing to send these
> envelope points as fingers, since they clearly are not. As a remedy,
> introduce MT_TOOL_ENVELOPE, which tells applications that care about
> details that these are not real fingers, at the same time as it allows
> gesture applications based on MT data to function without
> modification.

Is it assumed that the envelop has only two touches comprising it? Or is
it any number of touches? If it's any number of touches, how does one
know how many touches it is?

How are the envelop shape and position determined?

I think the idea is good, I just don't have enough information to
understand how the tool type is supposed to be used. This has been an
issue with many evdev properties, so I'm hoping we can provide more
detailed documentation this time around :).

-- Chase
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ