linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Rydberg <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: Peter Hutterer <peter.hutterer@who-t.net>,
	Andrew de los Reyes <andrew-vger@gizmolabs.org>,
	Hans de Goede <hdegoede@redhat.com>,
	jikos@jikos.cz, David Herrmann <dh.herrmann@gmail.com>,
	Linux Input <linux-input@vger.kernel.org>
Subject: Re: How to indicate hover touch when exact distance unknown?
Date: Wed, 08 Oct 2014 17:00:15 +0200	[thread overview]
Message-ID: <5435517F.9040507@euromail.se> (raw)
In-Reply-To: <20141001162252.GA23115@dtor-glaptop>

Hi Dmitry,


> OK, so should we then say that we will continue reporting binary hovering
> with ABS_MT_DISTANCE 0/1 and such devices must report resolution of 0;
> devices reporting wider ABS_MT_DISTANCE ranges should also report
> appropriate resolution, same as X/Y coordinates?

Yes, I think this makes sense, after all.

Thanks,
Henrik


  reply	other threads:[~2014-10-08 14:58 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
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 [this message]
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=5435517F.9040507@euromail.se \
    --to=rydberg@euromail.se \
    --cc=andrew-vger@gizmolabs.org \
    --cc=benjamin.tissoires@gmail.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 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).