On Tue, Sep 23, 2014 at 08:52:12PM +0200, Henrik Rydberg wrote:
quoted
quoted
quoted
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