From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Benedikt Spranger" <b.spranger@linutronix.de>
Cc: "linux-kernel @ vger. kernel. org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] simplify touchscreen event dispatcher
Date: Thu, 21 Jun 2007 13:24:20 -0400 [thread overview]
Message-ID: <d120d5000706211024m5a8439fcif7912a13c1e461c7@mail.gmail.com> (raw)
In-Reply-To: <20070621191530.75b0a9a6.b.spranger@linutronix.de>
Hi Benedikt,
On 6/21/07, Benedikt Spranger <b.spranger@linutronix.de> wrote:
> Fix the reporting order of BTN_TOUCH to coordinates first, then
> BTN_TOUCH. This simplifies touchscreen event dispatcher. The userspace
> should count on the kernel and get BTN_TOUCH-events with updated
> coordinates.
>
Why is this needed? In fact, I think that original way is better - you
can ignore coordinate events until you get BTN_TOUCH event. You do
rely on EV_SYN/SYN_REPORT to indicate end of the state transmission,
don't you?
--
Dmitry
parent reply other threads:[~2007-06-21 17:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070621191530.75b0a9a6.b.spranger@linutronix.de>]
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=d120d5000706211024m5a8439fcif7912a13c1e461c7@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=b.spranger@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®