From: Gerd Hoffmann <kraxel@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: spice-devel <spice-devel@lists.freedesktop.org>,
Avi Kivity <avi@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] paravirtual mouse/tablet
Date: Fri, 14 Jan 2011 16:13:29 +0100 [thread overview]
Message-ID: <4D306819.80405@redhat.com> (raw)
In-Reply-To: <108D35F5-7E49-4598-8903-599190A885E1@suse.de>
Hi,
> So it'd end up being (x,y,pressure) N times (I think 16 is fine for
> the foreseeable future).
I'd tend to extend MOVE to (x,y,pressure,index) and send N events with
the same timestamp. Needs to send only as many events as it finds
fingers on the touchpad, i.e. usually just one or two, even if the
protocol can easily handle alot more than 16 ;)
For a simple tablet pressure and index would just be 0.
> The details of what exactly that means
> should be figured out by the guest driver.
Agree.
> I'm not familiar with the hardware interface, but in order to support
> that the background interface must be a lot more complex than a
> simple button press.
Buttons events are for buttons. Real ones, which apple lost ;)
Of course a tap on the trackpad is usually interpreted as mouse click.
But that is the job of the guest OS, our virtual hardware doesn't care.
> But then again - how would we forward fine-grained scrolling to the
> guest if we only know that it's scrolling, but not what the actual
> presses on the touchpad looked like? Ugh.
There must be an interface to get (more or less) the raw touchpad data,
for apps which want implement their own multitouch gestures?
cheers,
Gerd
next prev parent reply other threads:[~2011-01-14 15:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 10:19 [Qemu-devel] paravirtual mouse/tablet Gerd Hoffmann
2011-01-13 11:01 ` [Qemu-devel] Re: [Spice-devel] " Stefan Hajnoczi
2011-01-13 11:51 ` Gerd Hoffmann
2011-01-13 15:55 ` Anthony Liguori
2011-01-13 17:08 ` Gerd Hoffmann
2011-01-13 20:41 ` Anthony Liguori
2011-01-14 8:49 ` Gerd Hoffmann
2011-01-14 10:48 ` Daniel P. Berrange
2011-01-14 14:14 ` Anthony Liguori
2011-01-14 14:28 ` Alon Levy
2011-01-14 14:52 ` Daniel P. Berrange
2011-01-14 16:10 ` [Spice-devel] [Qemu-devel] " Alon Levy
2011-01-13 15:52 ` [Qemu-devel] " Anthony Liguori
2011-01-13 16:14 ` Avi Kivity
2011-01-13 16:39 ` Anthony Liguori
2011-01-13 17:09 ` Paolo Bonzini
2011-01-13 20:38 ` Anthony Liguori
2011-01-13 17:13 ` Alexander Graf
2011-01-13 20:43 ` Anthony Liguori
2011-01-14 11:27 ` Gerd Hoffmann
2011-01-14 14:36 ` Alexander Graf
2011-01-14 14:56 ` [Spice-devel] " Frédéric Grelot
2011-01-14 15:13 ` Gerd Hoffmann [this message]
2011-01-14 15:28 ` Alexander Graf
2011-01-14 15:44 ` Alexander Graf
2011-01-14 16:31 ` Gerd Hoffmann
2011-01-14 16:42 ` Alexander Graf
2011-01-17 7:48 ` Gerd Hoffmann
2011-01-18 19:57 ` Alexander Graf
2011-01-15 12:07 ` Alon Levy
2011-01-14 15:37 ` Anthony Liguori
2011-01-14 16:26 ` Gerd Hoffmann
2011-01-14 17:02 ` Peter Maydell
2011-01-17 8:14 ` Gerd Hoffmann
2011-01-13 16:18 ` Avi Kivity
2011-01-13 16:43 ` Anthony Liguori
2011-01-13 17:19 ` Gerd Hoffmann
2011-01-13 19:21 ` Avi Kivity
2011-01-13 19:55 ` [Qemu-devel] Re: [Spice-devel] " Alon Levy
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=4D306819.80405@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@lists.freedesktop.org \
/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).