From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=55757 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PdhsE-0001HZ-3c
	for qemu-devel@nongnu.org; Fri, 14 Jan 2011 06:31:19 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Pdhs6-0001ON-3E
	for qemu-devel@nongnu.org; Fri, 14 Jan 2011 06:31:10 -0500
Received: from mx1.redhat.com ([209.132.183.28]:46562)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Pdhs5-0001O6-Ev
	for qemu-devel@nongnu.org; Fri, 14 Jan 2011 06:31:10 -0500
Message-ID: <4D30332F.2070003@redhat.com>
Date: Fri, 14 Jan 2011 12:27:43 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] paravirtual mouse/tablet
References: <4D2ED1C8.7070304@redhat.com> <4D2F1FA3.5030701@codemonkey.ws>
	<4D2F24EE.6070505@redhat.com> <4D2F2AB3.4020907@codemonkey.ws>
	<C1B91D17-6069-4E4C-9258-440800881A96@suse.de>
In-Reply-To: <C1B91D17-6069-4E4C-9258-440800881A96@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

   Hi,

> * multitouch capabilities would be good to design in a mouse protocol
> for 2011, so having say 16 x/y pairs would be better

Point.  What do we need here?  Finger $n down, finger $n up, finger $n 
moved to $x,$y?  Does it make sense to just add this to the 
move+buttonup/down structs?  Or should it better be separate?

> * on mac os at least scrolling is not done by pressing virtual
> buttons, but by having a separate scroll interface that knows about
> velocity and such - maybe worth adding that to the protocol from the
> beginning too.

Is that actually done by the hardware?  I'd expect macos processes the 
multitouch events, then provides this (finger $n moves this fast into 
that direction) as high-level interface, so this isn't something we have 
to care about at virtual hardware level.

cheers,
   Gerd