From: Peter Hutterer <peter.hutterer@who-t.net>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: "J.R. Mauro" <jrm8005@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: Add a detailed multi-touch finger data report protocol
Date: Tue, 11 Nov 2008 14:08:09 +1000 [thread overview]
Message-ID: <20081111040808.GA6776@dingo.redhat.com> (raw)
In-Reply-To: <49145628.7030804@euromail.se>
On Fri, Nov 07, 2008 at 03:52:24PM +0100, Henrik Rydberg wrote:
> > Have you worked with MPX? Or was a vanilla-X11 driver simple enough?
> > How does this all get presented to userspace applications? Multiple
> > mouse inputs or special stuff that applications would need a rewrite
> > to leverage?
>
> MPX is about making use of multiple pointers. The MT protocol is about
> making use of multiple fingers. It can in principle be used as input
> to MPX applications; I will bring it up with Peter Hutterer. However,
> the main aim is to bring advanced gestures to the linux desktop.
MPX is about making use of multiple input devices simultaneously and most of
the groundwork to get MT devices going is already there. From X's point of
view we need a bunch of new events to be sent to clients (and the bells and
whistles around it). The hard bit here is deciding which client to send the
events to.
I'd also say that an MT device should be presented as a single device with
multiple input points rather than as multiple separate devices.
This does require to rewrite applications (or at least slot some intermediate
layer in between), but having multitouch look like multi-mouse is a really bad
idea.
Cheers,
Peter
next prev parent reply other threads:[~2008-11-11 4:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 11:15 [PATCH] input: Add a detailed multi-touch finger data report protocol Henrik Rydberg
2008-11-07 13:34 ` J.R. Mauro
2008-11-07 14:26 ` Henrik Rydberg
2008-11-07 14:36 ` J.R. Mauro
2008-11-07 14:52 ` Henrik Rydberg
2008-11-07 14:57 ` J.R. Mauro
2008-11-07 15:07 ` Henrik Rydberg
2008-11-11 4:08 ` Peter Hutterer [this message]
2008-11-08 0:51 ` Arjan Opmeer
2008-11-08 10:43 ` Henrik Rydberg
2008-11-08 11:29 ` Arjan Opmeer
2008-11-08 12:02 ` Henrik Rydberg
2008-11-11 4:13 ` Peter Hutterer
2008-11-11 4:20 ` Peter Hutterer
2008-11-11 11:19 ` Henrik Rydberg
2008-11-19 16:37 ` Dmitry Torokhov
2008-11-19 16:54 ` Jim Gettys
2008-11-19 23:34 ` Henrik Rydberg
2008-11-21 14:43 ` Jim Gettys
2008-11-19 23:31 ` Henrik Rydberg
2008-11-21 14:44 ` Henrik Rydberg
2008-11-21 16:04 ` 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=20081111040808.GA6776@dingo.redhat.com \
--to=peter.hutterer@who-t.net \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jrm8005@gmail.com \
--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).