From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ping Cheng <pinglinux@gmail.com>
Cc: linux-kernel@vger.kernel.org, jkosina@suse.cz,
Ping Cheng <pingc@wacom.com>
Subject: Re: [PATCH] Add BTN_TOOL_BUTTONS to input.h
Date: Sun, 21 Nov 2010 23:55:55 -0800 [thread overview]
Message-ID: <20101122075554.GA27300@core.coreip.homeip.net> (raw)
In-Reply-To: <1290126335-12430-1-git-send-email-pingc@wacom.com>
Hi Ping,
On Thu, Nov 18, 2010 at 04:25:35PM -0800, Ping Cheng wrote:
> We "borrowed" BTN_TOOL_FINGER from input/mouse to pass tablet
> buttons to the user land. This has not been an issue since
> tablet was not considered as a mouse replacement. With the
> introduction of hybrid digitizer and touch devices, the tool
> type is causing confusion. A new tool type is due for the
> well-being of future input device drivers.
>
I am sorry but I do not understand the reasoning behind
BTN_TOOL_BUTTONS.
The BTN_TOOL_* were introduced to indicate to the userspace tool that is
currently touching the surface of the device. Buttons are expected to be
always present and can change their state regardless of what tool is
being used at the moment. I.e. The full hardware state (between
EV_SYN/SYN_REPORT) could be, for example,
Pen at 10,20, BTN_0, and BTN_2 (ABS_X 10, ABS_Y 20, BTN_TOOL_PEN, BTN_0,
BTN_2) or
Lens at 20,15 and BTN_1 (ABS_X 20, ABS_Y 15, BTN_TOOL_LENS, BTN_1).
As you can see BTN_* events can accompany either BTN_TOOL_LENS or
BTN_TOOL_PEN or any other BTN_TOOL_*.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-11-22 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 0:25 Ping Cheng
2010-11-22 7:55 ` Dmitry Torokhov [this message]
2010-11-23 17:40 ` Ping Cheng
2010-11-23 22:24 ` Dmitry Torokhov
2010-11-24 0:12 ` Ping Cheng
2010-11-24 0:38 ` Dmitry Torokhov
2010-11-24 0:51 ` Ping Cheng
2010-11-24 1:10 ` Ping Cheng
2010-11-24 2:44 ` Dmitry Torokhov
2010-11-24 17:46 ` Ping Cheng
2010-11-24 20:16 ` Dmitry Torokhov
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=20101122075554.GA27300@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pingc@wacom.com \
--cc=pinglinux@gmail.com \
/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®