From: "Henrik Rydberg" <rydberg@euromail.se>
To: Peter Hutterer <peter.hutterer@who-t.net>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
chatty@enac.fr, chasedouglas@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Input: MT - Include win8 support
Date: Wed, 9 May 2012 07:35:02 +0200 [thread overview]
Message-ID: <20120509053502.GA30063@polaris.bitmath.org> (raw)
In-Reply-To: <20120508235219.GA4067@yabbi.redhat.com>
> > > > Looking at the figure, it is clear that the MT model has two centers,
> > > > one for each ellipse. Thus, center is not discriminating
> > > > enough. Perhaps ABS_MT_OUTER_X/Y is more appropriate, then?
> > >
> > > ABS_MT_OUTER_CENTER
> >
> > I appreciate the suggestion, but along two-word combinations,
> > ABS_MT_OUTER_POSITION would integrate better with existing names. Both
> > seem awfully long, though.
>
> problem I see with "outer position" is that I'd associate it with the
> top/left position of whatever "outer" is, not with the center of said
> envelope. that's why I'd argue that "center" should be somewhere in the
> name.
Top-left does not apply to an ellipse, so that argument makes little
sense for someone looking only at the MT protocol. Given that position
is the actual protocol name for the center of the touching ellipse,
there is hardly any doubt what it means in this context.
How about ABS_MT_TOOL_X/Y?
Henrik
next prev parent reply other threads:[~2012-05-09 5:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 15:08 [RFC] Input: MT - Include win8 support Henrik Rydberg
2012-05-05 20:07 ` Chase Douglas
2012-05-08 18:50 ` H. Peter Anvin
2012-05-08 19:37 ` Henrik Rydberg
2012-05-06 14:41 ` Benjamin Tissoires
2012-05-06 18:07 ` Henrik Rydberg
2012-05-06 18:28 ` Henrik Rydberg
2012-05-08 6:02 ` Peter Hutterer
2012-05-08 18:40 ` Henrik Rydberg
2012-05-08 23:52 ` Peter Hutterer
2012-05-09 5:35 ` Henrik Rydberg [this message]
2012-05-09 18:10 ` Ping Cheng
2012-05-09 19:39 ` 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=20120509053502.GA30063@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=benjamin.tissoires@gmail.com \
--cc=chasedouglas@gmail.com \
--cc=chatty@enac.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
/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