From: Chase Douglas <chase.douglas@canonical.com>
To: Henrik Rydberg <rydberg@euromail.se>
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 11:09:53 -0800 [thread overview]
Message-ID: <4CFFD801.8060704@canonical.com> (raw)
In-Reply-To: <4CFFD3FE.1090103@euromail.se>
On 12/08/2010 10:52 AM, Henrik Rydberg wrote:
>> As you noted, what we are really interested here is a bounding
>> rectangle. I think Ping has said that Wacom could provide something that
>> is similar to a real convex hull, and mixing the two concepts together
>> could cause another ambiguity like BTN_TOOL_DOUBLETAP :).
>
>
> True, we should work towards avoiding such ambiguities.
>
>> I suggest merely renaming this to MT_TOOL_RECT to avoid confusion.
This is really the main point I wanted to make, even though it was
hidden among other things :). Do you have thoughts here?
>> 2. We could provide for multiple simultaneous rects by using the value
>> of the MT_TOOL_RECT property. The first rect would have value 0, the
>> second would have value 1, etc. I don't know if this will ever be used
>> since most devices will have real MT soon enough, but it wouldn't hurt
>> to define this.
>
> I do think this is an unnecessary complication.
It's not really any complication. I think we should define what the
valid values are for MT_TOOL_{RECT,ENVELOPE} even if only one envelope
is supported. Thus, I don't see why we shouldn't allow for multiple
values for multiple rects.
Hardware manufacturers always seem to surprise us with what they come up
with too :).
-- Chase
next prev parent reply other threads:[~2010-12-08 19:10 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
2010-12-08 18:38 ` Chase Douglas
2010-12-08 18:52 ` Henrik Rydberg
2010-12-08 19:09 ` Chase Douglas [this message]
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=4CFFD801.8060704@canonical.com \
--to=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 \
--cc=rydberg@euromail.se \
/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