From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DDTbH-0000LW-Eq for qemu-devel@nongnu.org; Mon, 21 Mar 2005 15:34:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DDTbD-0000Jl-OW for qemu-devel@nongnu.org; Mon, 21 Mar 2005 15:34:09 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DDTbD-0000Gy-7C for qemu-devel@nongnu.org; Mon, 21 Mar 2005 15:34:07 -0500 Received: from [207.253.156.11] (helo=xavier.megacom.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DDTHr-00074I-TD for qemu-devel@nongnu.org; Mon, 21 Mar 2005 15:14:08 -0500 Received: from [127.0.0.1] (dial-112-112-113-216.megacom.net [216.113.112.112]) by xavier.megacom.net (8.12.10/8.12.10) with ESMTP id j2LKE4oT010346 for ; Mon, 21 Mar 2005 15:14:05 -0500 Message-ID: <423F2B0D.9050501@domn.net> Date: Mon, 21 Mar 2005 15:14:05 -0500 From: use.reply-to.address@domn.net MIME-Version: 1.0 Subject: Re: [Qemu-devel] Current state of RFB patch References: <000001c52d7c$c14b4f60$6401a8c0@geodb.org> <1111410939.423ec8fbe3365@imp5-q.free.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu@domn.net, 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 >Well, here you are: > >http://libvncserver.sf.net/qemu/qemu-rfb10.patch.gz > >Have fun! > >One remark, though: it is a quick hack to make it apply to the current >CVS, so to use your mouse, you have to make sure that the guest OS does >not accelerate your pointer. In Windows: in Settings, look for Mouse and >set it to "slowest". With x11: "xset m 1". > > is it possible to have qemu disable host mouse acceleration while it has focus ? some guest os do not allow disabling of acceleration for example in dos , some games have their own builtin mouse driver , and you can't control acceleration on those off course a generic vnc client can't do that , so maybe then there could be a de-acceleration routine in the qemu-vnc interface code ?