Re: [PATCH] Documented input device properties.
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2012-01-09 17:55:57
Hi Jussi, On Mon, Jan 09, 2012 at 06:44:14PM +0200, Jussi Pakkanen wrote:
quoted hunk ↗ jump to hunk
--- Documentation/input/event-codes.txt | 27 +++++++++++++++++++++++++++ 1 files changed, 27 insertions(+), 0 deletions(-)diff --git a/Documentation/input/event-codes.txt b/Documentation/input/event-codes.txt index 23fcb05..7c515a5 100644 --- a/Documentation/input/event-codes.txt +++ b/Documentation/input/event-codes.txt@@ -220,6 +220,33 @@ EV_PWR: EV_PWR events are a special type of event used specifically for power mangement. Its usage is not well defined. To be addressed later. +Device properties: +================= + +INPUT_PROP_POINTER: +------------------ +There is a one to one mapping between the device coordinates and +screen coordinates.
This is not correct as touchpads fall firmly into INPUT_PROP_POINTER land and certainly do not have 1:1 relationship between on-screen and device coordinates.
This property only has meaning for non-touch based +input such as a pen or an eraser. A drawing tablet would have this property +set.
Wacom Bamboo touch can be said is touch based but still is a pointer device. Basically pointer device is one that requires use of an on-screen pointer to reflect user's movement while with direct devices touching object itself serves as a pointer to the user. Thanks. -- Dmitry