From: Henrik Rydberg <rydberg@euromail.se>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: mt: Add an envelope tool type
Date: Wed, 08 Dec 2010 19:23:12 +0100 [thread overview]
Message-ID: <4CFFCD10.5030202@euromail.se> (raw)
In-Reply-To: <4CFFC3C2.1080905@canonical.com>
>> 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?
It could be any number of points, although, as you say, the exact semantics of
multiple points have not yet been defined/documented. Traditionally, a convex
hull is defined as a sequence of points, such that the last links to the first.
It makes sense to define the envelope points similarly. However, we can pass
that bridge as we get there. Right now, we have use for the two-point case. The
number is determined the same was as for fingers - count the number of active slots.
> How are the envelop shape and position determined?
I was imagining a convex polygon shape, but frankly, I see no immediate use for
anything but the bounding rectangle.
> 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 :).
Yes, it is a good point. The current patch at least documents the intended use,
and seems apt for the moment. We can always add more as the concept matures.
Thanks,
Henrik
next prev parent reply other threads:[~2010-12-08 18:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 11:29 [PATCH] input: mt: Add an envelope tool type Henrik Rydberg
2010-12-08 17:43 ` Chase Douglas
2010-12-08 18:23 ` Henrik Rydberg [this message]
2010-12-08 18:38 ` Chase Douglas
2010-12-08 18:52 ` Henrik Rydberg
2010-12-08 19:09 ` Chase Douglas
2010-12-08 19:23 ` Henrik Rydberg
2010-12-08 19:53 ` Mohamed Ikbel Boulabiar
[not found] ` <AANLkTi=iw+7CDhbO4N9rMVSwS0t93BaaBVgoAwz-GeHo@mail.gmail.com>
2010-12-08 20:02 ` Henrik Rydberg
2010-12-08 20:17 ` Mohamed Ikbel Boulabiar
2010-12-08 20:44 ` Chase Douglas
2010-12-08 23:43 ` Ping Cheng
2010-12-08 23:58 ` Dmitry Torokhov
2010-12-09 0:06 ` Ping Cheng
2010-12-09 1:18 ` Henrik Rydberg
2010-12-09 1:22 ` Ping Cheng
2010-12-09 1:38 ` Mohamed Ikbel Boulabiar
2010-12-09 1:51 ` Henrik Rydberg
2010-12-09 1:12 ` Henrik Rydberg
2010-12-09 1:17 ` Dmitry Torokhov
2010-12-09 1:24 ` Henrik Rydberg
2010-12-09 1:20 ` Ping Cheng
2010-12-09 2:01 ` Henrik Rydberg
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=4CFFCD10.5030202@euromail.se \
--to=rydberg@euromail.se \
--cc=chase.douglas@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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