From: WaxDragon <waxdragon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU keyboard issue with Gujin-2.2
Date: Sat, 13 Oct 2007 22:12:02 -0400 [thread overview]
Message-ID: <9b0d5f320710131912i1b4ef3a7lbe5c7e1d6dcbda80@mail.gmail.com> (raw)
In-Reply-To: <691521.34631.qm@web26908.mail.ukl.yahoo.com>
On 10/11/07, Etienne Lorrain <etienne_lorrain@yahoo.fr> wrote:
> Hello,
>
> I did more search on the keyboard problem, just posted on the forum
> but here seems to be a better place:
>
This may not be the same issue, but I've seen strange behaviour
also. ReactOS has a built in kernel debugger that seems to have a
problem with the mouse input. If the mouse is "grabbed" by the QEMU
SDL window, and you are in the kernel debugger, moving the mouse will
generate "garbage" charaters, usually rendering the debugger useless.
Real hardware, VMWare, and QEMU *without* the mouse grabbed do not
exhibit this behaviour.
QEMU has acted this way for quite some time, seems forever. I've
mentioned it on #qemu to little interest, but since it's not a huge
issue for me, I've not looked into a great deal. Thought I would
mention it.
WaxDragon
--
22:38 <@WaxDragon> false ^ true
22:39 < false> :(
22:39 < false> dont you think you can XOR me and get away with it! I
always return!
next prev parent reply other threads:[~2007-10-14 2:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 8:49 [Qemu-devel] QEMU keyboard issue with Gujin-2.2 Etienne Lorrain
2007-10-14 2:12 ` WaxDragon [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-24 10:07 Alexander E. Patrakov
2007-09-24 17:37 ` Stefan Weil
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=9b0d5f320710131912i1b4ef3a7lbe5c7e1d6dcbda80@mail.gmail.com \
--to=waxdragon@gmail.com \
--cc=qemu-devel@nongnu.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).