From: Chris Bagwell <chris@cnpbagwell.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: mt: Identify pointer emulation contact
Date: Fri, 10 Dec 2010 09:11:13 -0600 [thread overview]
Message-ID: <AANLkTin+b_04qcOcFmP+0tYHCibvHHearfFXZJAb4R5R@mail.gmail.com> (raw)
In-Reply-To: <4D01D6AF.6010202@euromail.se>
On Fri, Dec 10, 2010 at 1:28 AM, Henrik Rydberg <rydberg@euromail.se> wrote:
>>
>
>> So how do you propose userspace will use it? Obviously it will not help
>> old dumb (ST) applications and new smart applications should understand
>> MT protocol and thus do not need to pay much attention to ST events
>> anyway. Apparently you have some new dumb userspace in mind here?
>
>
> You are right, it is a dumb idea. Consider this one dropped.
If anyone is working on clickpad support, they may want to keep this
idea in mind. I guess I mean working on clickpads and with simple ST
apps.
If user clicks with one finger, I think currently that user expects
dragging that one finger will move cursor still (click-and-drag). I'd
think its more usable though to click with one finger and drag with
the other. During this use case we need to switch pointer tracking
from one finger to the other.
Sending a new tracking ID is an easy way to inform apps about expected
jump in values during switch. I thought of things like
BTN_TOOL_FINGER=0; sync; BTN_TOOL_FINGER=1 but that looks like tapping
is occurring.
Anyways, as you suggestion, this can be solved by forcing apps to
process MT events so not to big a deal long term.
Chris
prev parent reply other threads:[~2010-12-10 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 23:19 [PATCH] input: mt: Identify pointer emulation contact Henrik Rydberg
2010-12-09 23:49 ` Dmitry Torokhov
2010-12-10 7:28 ` Henrik Rydberg
2010-12-10 15:11 ` Chris Bagwell [this message]
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=AANLkTin+b_04qcOcFmP+0tYHCibvHHearfFXZJAb4R5R@mail.gmail.com \
--to=chris@cnpbagwell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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).