From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DpP1U-0002aA-1G for qemu-devel@nongnu.org; Mon, 04 Jul 2005 07:22:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DpP1N-0002WV-88 for qemu-devel@nongnu.org; Mon, 04 Jul 2005 07:21:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DpP0k-0001sy-JO for qemu-devel@nongnu.org; Mon, 04 Jul 2005 07:21:14 -0400 Received: from [202.123.2.25] (helo=iron2.intnet.mu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DpOnE-0001nQ-VT for qemu-devel@nongnu.org; Mon, 04 Jul 2005 07:07:17 -0400 Message-ID: <42C91488.7050402@secureit-mu.com> Date: Mon, 04 Jul 2005 14:50:48 +0400 From: Josef Moffett MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: Qemu Windows Host & Client Feedback References: <23bcb87005063014284513c1d0@mail.gmail.com> <23bcb87005070322535a8cacac@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Christian Walther wrote: > Doctor Bill wrote: > >> Even with the snapshot version, the same mapping problem occurs >> sometimes. >> Usually, it is after a soft reboot. For example, if I restart from >> Windows 98 se to >> DOS and then back to Windows 98 se then I get the key mapping where keys >> act as hot keys regardless of focus. However, I have experienced a >> few times >> when the keyboard started off in that mode. The general workaround >> seems to >> be to do a shutdown of the virtual machine and then restart QEMU. > > > Could this be a case of stuck modifier keys? Qemu's notion of which > modifier keys are pressed can sometimes get out of sync with the real > state of the keys. E.g. when you press the alt key to alt-tab away > from qemu, it still thinks that the alt key is pressed afterwards, > because it didn't receive the key-up event, not having focus at that > point. This can be corrected by pressing and releasing the stuck > modifier key after you switch back to Qemu. > > -Christian > > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel I have noticed a similar "problem" with the numlock. It doesn't actually bother me as the solution is very simple, but when I start qemu with the numlock switched on then in qemu to get numlock on I have to turn it 'off' (ie no led on the keyboard) and vice versa. Just a comment, about the keyboard state, perhaps in final polishing this may be considered important, but in actual doing stuff with qemu it doesn't actually reduce workability. Cheers Joe