From: Nikolai Kondrashov <spbnick@gmail.com>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>,
Chris Bagwell <chris@cnpbagwell.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: Add evdev type and code definitions
Date: Sat, 08 Jan 2011 01:26:45 +0300 [thread overview]
Message-ID: <4D279325.3040205@gmail.com> (raw)
In-Reply-To: <4D279075.4080503@canonical.com>
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.
Sincerely,
Nick
next prev parent reply other threads:[~2011-01-07 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 21:28 [PATCH v2] Documentation: Add evdev type and code definitions Chase Douglas
2011-01-07 21:53 ` Dmitry Torokhov
2011-01-07 22:03 ` Chase Douglas
2011-01-07 22:42 ` Dmitry Torokhov
2011-01-07 22:06 ` Nikolai Kondrashov
2011-01-07 22:15 ` Chase Douglas
2011-01-07 22:26 ` Nikolai Kondrashov [this message]
2011-01-07 22:36 ` Chase Douglas
2011-01-08 1:15 ` Chris Bagwell
2011-01-09 14:51 ` Henrik Rydberg
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=4D279325.3040205@gmail.com \
--to=spbnick@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=chris@cnpbagwell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).