From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Andrew de los Reyes <andrew-vger@gizmolabs.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
hdegoede@redhat.com, jikos@jikos.cz,
David Herrmann <dh.herrmann@gmail.com>,
peter.hutterer@who-t.net,
Linux Input <linux-input@vger.kernel.org>
Subject: Re: How to indicate hover touch when exact distance unknown?
Date: Tue, 23 Sep 2014 17:27:12 -0700 [thread overview]
Message-ID: <20140924002712.GB16747@core.coreip.homeip.net> (raw)
In-Reply-To: <5421C15C.6030302@euromail.se>
On Tue, Sep 23, 2014 at 08:52:12PM +0200, Henrik Rydberg wrote:
> >>> So I am not very happy with having a new
> >>> tool. In the end, it may also disturb older clients which will not know
> >>> what to do with HOVER.
> >>> And the ABS_MT_DISTANCE approach used to be fully retro-compatible
> >>> (assuming that the hovering distance is small enough for the user not to
> >>> detect it).
> >>
> >> Except that if we start getting devices that can actually tell the
> >> distance we'd need special casing 0/1 handling, no?
>
> Logically, a hovering object which does not support real distance reporting
> would simply be present in the contact list but have ABS_MT_TOUCH = 0. However,
> I do not think all layers of the stack supports this notion.
That unfortunately does not give us indication whether device supports
hover or not: we'll know only when we see it.
--
Dmitry
next prev parent reply other threads:[~2014-09-24 0:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG_cf+dJfiqW_V1k4MfGMBNUK9Kgc4=9BPAuum7dbs6rkmAgrQ@mail.gmail.com>
2014-09-23 14:59 ` How to indicate hover touch when exact distance unknown? Benjamin Tissoires
2014-09-23 16:28 ` Dmitry Torokhov
2014-09-23 16:46 ` Andrew de los Reyes
2014-09-23 18:52 ` Henrik Rydberg
2014-09-24 0:27 ` Dmitry Torokhov [this message]
2014-09-24 4:52 ` Peter Hutterer
2014-09-24 5:28 ` Henrik Rydberg
2014-09-26 13:50 ` Benjamin Tissoires
2014-10-01 16:22 ` Dmitry Torokhov
2014-10-08 15:00 ` Henrik Rydberg
2014-09-26 4:07 Chung-Yih Wang (王崇懿)
-- strict thread matches above, loose matches on Subject: below --
2014-09-23 14:37 Andrew de los Reyes
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=20140924002712.GB16747@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=andrew-vger@gizmolabs.org \
--cc=benjamin.tissoires@redhat.com \
--cc=dh.herrmann@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jikos@jikos.cz \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--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).