From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CqYvp-0005pW-2Z for qemu-devel@nongnu.org; Mon, 17 Jan 2005 10:36:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CqYvk-0005mY-C7 for qemu-devel@nongnu.org; Mon, 17 Jan 2005 10:36:37 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CqYvk-0005lb-0y for qemu-devel@nongnu.org; Mon, 17 Jan 2005 10:36:36 -0500 Received: from [38.113.3.61] (helo=smtp-out.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CqYiv-0006No-Vz for qemu-devel@nongnu.org; Mon, 17 Jan 2005 10:23:22 -0500 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by smtp-out.hotpop.com (Postfix) with SMTP id 33D9BCFEA17 for ; Mon, 17 Jan 2005 15:23:19 +0000 (UTC) Received: from jbrown.mylinuxbox.org (pcp03144805pcs.midval01.tn.comcast.net [68.59.228.236]) by smtp-3.hotpop.com (Postfix) with ESMTP id 27ABE134DE68 for ; Mon, 17 Jan 2005 15:23:18 +0000 (UTC) Date: Mon, 17 Jan 2005 10:22:10 -0500 From: "Jim C. Brown" Subject: Re: [Qemu-devel] rfb patch and mouse movement Message-ID: <20050117152210.GA5897@jbrown.mylinuxbox.org> References: <41EA36B5.4020302@wasp.net.au> <20050116143509.GA31097@jbrown.mylinuxbox.org> <41EB3DC0.7040804@wasp.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41EB3DC0.7040804@wasp.net.au> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Mon, Jan 17, 2005 at 08:23:28AM +0400, Brad Campbell wrote: > Jim C. Brown wrote: > > >>It worked by taking the data from the touchscreen, running it through the > >>relevant calibration routines and sending windows absolute mouse movement > >>messages. It worked rather well. > > > > > >What "relevant calibration routines" are we looking at here? > > Pretty simple linear scaling and axis inversion for touchscreens. Nothing > complex. Just calculate the max/min points based on some calibration, scale > them up to 16 bit values and feed them to windows using a mouse movement > message. > > >>Perhaps we could use the touchscreen for movement only > >>and send clicks over the ps2 interface. > > > > > >That would require an ugly custom guest driver. > > Not really. Touchscreen drivers and mouse drives co-exist. Just send the > movement down the touch screen line and the clicks down the PS2 line. > Simple. > Hmm .. if hardware which uses this method already exists, then it's a different story. Still, unless the calibration problem is solved, not worth the trouble. > > Regards, > Brad > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.