All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Henrik Rydberg" <rydberg@euromail.se>
To: Ping Cheng <pinglinux@gmail.com>
Cc: Mohamed Ikbel Boulabiar <boulabiar@gmail.com>,
	Linux Input <linux-input@vger.kernel.org>
Subject: Re: [PATCH] Input: wacom - Add POINTER and DIRECT device properties
Date: Fri, 16 Sep 2011 12:50:36 +0200	[thread overview]
Message-ID: <20110916105036.GA4455@polaris.bitmath.org> (raw)
In-Reply-To: <CAF8JNhKFz8-bJ4HMguU2qReageX4WBB1bWR0amRbYmaujNVX8A@mail.gmail.com>

> > I think the bottom line is that even if the "directness" of a device
> > is configurable, it still needs to have a default. Moreover, the
> > notion of kernel mode settings could be applicable here too.
> 
> Talking about default mode, there are cases that the mode is decided
> by the tools running on the device/tablet, instead of the tablet
> itself.
> 
> Take Wacom's Intuos and Graphire series for example, those tablets
> support both styli and mice. For styli, the default is absolute mode;
> while for mice, it is relative. So, only valid property the tablet can
> tell the user-land is: I am a tablet, i.e., not a touchscreen. Clients
> have to check the tool types to set the default mode to relative
> (BTN_TOOL_MOUSE/LENS) or absolute (BTN_TOOL_PEN/AIRBRUSH/RUBBER...).

And those modes can be determined using the available axes. However,
when all axes are the same, a statement like "I am a tablet" does not
exist. In that case, distinguishing between touchscreen, touchpad and
tablet becomes a question of interpreting the properties. Such a
distinction cannot be achieved using a single bit of information, and
that was never the intention.

In short: I think Chris' comments are spot on, and incorporating them
into the patch would be good to avoid further confusion.

Thanks,
Henrik

  reply	other threads:[~2011-09-16 10:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 16:00 [PATCH] Input: wacom - Add POINTER and DIRECT device properties Jason Gerecke
2011-09-01 19:31 ` Ping Cheng
2011-09-13  8:09 ` Henrik Rydberg
2011-09-13  8:19   ` Mohamed Ikbel Boulabiar
2011-09-13 14:13   ` Chris Bagwell
2011-09-13 17:36     ` Ping Cheng
2011-09-13 20:54       ` Chris Bagwell
2011-09-16 23:10     ` Jeffrey Brown
2011-09-17 11:44       ` Henrik Rydberg
     [not found]   ` <CAPHpN5OAPdPQ1SmwrGT6pMvgWESBOSnRvb0jKUszkU_31MFXWg@mail.gmail.com>
2011-09-14  7:15     ` Henrik Rydberg
2011-09-15 16:16       ` Ping Cheng
2011-09-16 10:50         ` Henrik Rydberg [this message]
2011-09-16 21:45           ` Jason Gerecke
2011-09-17 11:21             ` Henrik Rydberg
2011-09-19 23:40               ` Chase Douglas
2011-09-20  1:05                 ` Jeffrey Brown
2011-09-20  2:49                   ` Chase Douglas
2011-09-21 11:42                     ` 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=20110916105036.GA4455@polaris.bitmath.org \
    --to=rydberg@euromail.se \
    --cc=boulabiar@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.