linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Bagwell <chris@cnpbagwell.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Ping Cheng <pinglinux@gmail.com>, linux-input@vger.kernel.org
Subject: Re: [PATCH 2/2]input - wacom_w8001: Add one finger touch support
Date: Fri, 10 Dec 2010 07:47:36 -0600	[thread overview]
Message-ID: <AANLkTimM9stMm8zKbjyRV5BpsV9m1s6EBATMZXbf-+5W@mail.gmail.com> (raw)
In-Reply-To: <20101210073813.GB21009@core.coreip.homeip.net>

On Fri, Dec 10, 2010 at 1:38 AM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> On Thu, Dec 09, 2010 at 03:21:34PM -0600, Chris Bagwell wrote:
>>
>> For first point, your right that (123,78) is just a good "known
>> starting value" if a driver is going to use that concept because it
>> could be filtered just as easy as (0,0).
>
> I am afraid I did not explain myself well enough. (0,0) is valid
> coordinate, same as (123, 78). Thus, even if we try to make driver send
> (0,0, !touch), input core may suppress it and never deliver to
> userspace if last touching point happened to be also (0,0). Thus
> userspace should not rely on having coordinates reset I think.
>

I had understood ya.  What I meant is if a driver sends (0,0,!touch)
and a sync when switching tools then you do not need to buffer
previous values but instead can imply what previous values are.
Userland would still need to account for case of filtered events.  Its
a memset() vs. a memcpy() when switching tools.

Anyways,  I'm not recommending any behavior; just letting you know
some existing assumptions on driver behavior.

Thanks,
Chris

  reply	other threads:[~2010-12-10 13:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  1:23 [PATCH 2/2]input - wacom_w8001: Add one finger touch support Ping Cheng
2010-12-09  6:44 ` Dmitry Torokhov
2010-12-09 17:39   ` Ping Cheng
2010-12-09 18:02     ` Dmitry Torokhov
2010-12-09 15:06 ` Chris Bagwell
2010-12-09 19:36   ` Ping Cheng
2010-12-09 19:50     ` Dmitry Torokhov
2010-12-09 21:21       ` Chris Bagwell
2010-12-10  1:29         ` Ping Cheng
2010-12-10 13:39           ` Chris Bagwell
2010-12-10  7:38         ` Dmitry Torokhov
2010-12-10 13:47           ` Chris Bagwell [this message]
2010-12-10 17:37             ` Ping Cheng

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=AANLkTimM9stMm8zKbjyRV5BpsV9m1s6EBATMZXbf-+5W@mail.gmail.com \
    --to=chris@cnpbagwell.com \
    --cc=dmitry.torokhov@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 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).