From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Ping Cheng <pingc@wacom.com>
Subject: Re: [PATCH] input: mt: Add hovering distance axis
Date: Wed, 8 Dec 2010 10:05:21 -0800 [thread overview]
Message-ID: <20101208180521.GA31522@core.coreip.homeip.net> (raw)
In-Reply-To: <4CFFC45C.2040107@canonical.com>
On Wed, Dec 08, 2010 at 09:46:04AM -0800, Chase Douglas wrote:
> On 12/07/2010 12:27 AM, Henrik Rydberg wrote:
> > Touch devices capable of hovering, i.e., fingers detected a distance
> > from the surface, are not supported by the current input MT
> > protocol. This patch adds ABS_MT_DISTANCE, which may be used to
> > indicate the distance between the contact and the surface.
>
> Have you given thought to calling it ABS_MT_Z instead? I have no real
> problem with ABS_MT_DISTANCE per se, but ABS_MT_Z is more clearly
> defined in my head. If I was new to MT development I may wonder if
> ABS_MT_DISTANCE had anything to do with distance between points or some
> other object.
X/Y/Z imply that we fully engaged the device and it is 3 dimensional.
Distance says that we are approaching the device but have not directly
engaged it yet.
I think ABS_DISTANCE was added at Pings request and ABS_MT_DISTANCE is
modeled after ST one. Ping, could you refresh my memory why we needed
ABS_DISTANCE?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-12-08 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 8:27 [PATCH] input: mt: Add hovering distance axis Henrik Rydberg
2010-12-07 10:41 ` Dmitry Torokhov
2010-12-08 17:46 ` Chase Douglas
2010-12-08 18:05 ` Dmitry Torokhov [this message]
2010-12-08 18:16 ` Henrik Rydberg
2010-12-08 18:20 ` Ping Cheng
2010-12-08 18:40 ` Henrik Rydberg
2010-12-08 23:31 ` Ping Cheng
2010-12-08 23:54 ` Dmitry Torokhov
2010-12-09 0:08 ` Ping Cheng
2010-12-09 0:13 ` Dmitry Torokhov
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=20101208180521.GA31522@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pingc@wacom.com \
--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;
as well as URLs for NNTP newsgroup(s).