From: Henrik Rydberg <rydberg@euromail.se>
To: Andrew de los Reyes <andrew-vger@gizmolabs.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: 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 20:52:12 +0200 [thread overview]
Message-ID: <5421C15C.6030302@euromail.se> (raw)
In-Reply-To: <CAG_cf+fuugk4QK_1BtWnJWzunWT4QeSus_2cuPpYH_8UCUjMOQ@mail.gmail.com>
>>> 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.
Henrik
next prev parent reply other threads:[~2014-09-23 19:10 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 [this message]
2014-09-24 0:27 ` Dmitry Torokhov
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=5421C15C.6030302@euromail.se \
--to=rydberg@euromail.se \
--cc=andrew-vger@gizmolabs.org \
--cc=benjamin.tissoires@redhat.com \
--cc=dh.herrmann@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jikos@jikos.cz \
--cc=linux-input@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.