[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D279589.1060107@canonical.com>
Date: Fri, 07 Jan 2011 17:36:57 -0500
From: Chase Douglas <chase.douglas@...onical.com>
To: Nikolai Kondrashov <spbnick@...il.com>
CC: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Henrik Rydberg <rydberg@...omail.se>,
Chris Bagwell <chris@...bagwell.com>,
Peter Hutterer <peter.hutterer@...-t.net>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] Documentation: Add evdev type and code definitions
On 01/07/2011 05:26 PM, Nikolai Kondrashov wrote:
> On 01/08/2011 01:15 AM, Chase Douglas wrote:
>> Hmm.. That seems incorrect to me. Why wouldn't it follow the behavior
>> outlined above?
> Because the tablet doesn't report when the tool enters/leaves the proximity.
> It just starts/stops sending the coordinates.
>
> A leave timer could be used, though. Maybe we could ignore the case when the
> mouse is laying still on the tablet or the pen is held very steadily in
> place and just tell that tool left the surface.
>
> Maybe it will be beneficial to have it synthesised after all, as it would
> probably ease the integration with xf86-input-wacom and will keep the evdev
> protocol more consistent.
I think I understand now, and it sounds pretty broken :). Do we want to
codify such behaviour, or leave it out as a special case? I don't see
this document as a definitive guide to evdev usage and driver
development, just a reference and best practices guide, so I'm inclined
to say the latter.
-- Chase
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists