From: Oliver Gerlich <olig9@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU 0.8.1
Date: Fri, 05 May 2006 12:33:47 +0200 [thread overview]
Message-ID: <445B2A0B.7020501@gmx.de> (raw)
In-Reply-To: <4D5D7ECC-9895-466F-BEF5-6FD465202C12@claunia.com>
Natalia Portillo wrote:
> That requires a driver in guest side that communicates with qemu.
>
> VMWare and VirtualPC does this but requires a driver in the guest side,
> so in unsupported systems you still have to click to grab.
Just as a side note, the USB tablet support makes this quite easy at
least on Win2k - it already has the required driver, so for me it was
enough to add -usbdevice tablet to the command line to have the mouse
cursor automatically grabbed/ungrabbed (it seems that the behaviour of
Ctrl+Alt changed a bit, but one gets used to it).
Thanks to Brad and Anthony for making that possible :D
Regards,
Oliver
>
> El 05/05/2006, a las 8:57, Christian MICHON escribió:
>
>> it works. Side effect: after the first ungrab, I can't see the host
>> pointer over the SDL windows.
>>
>> Yet, it's nothing as compared to the invisible wall.
>> I know nothing about most qemu internals, but would it be
>> possible to make it like vmw*re, ie the mouse is automagically
>> grabbed/ungrabbed whenever you reach the limits of the
>> SDL window ?
>>
>> On 5/5/06, Anthony Liguori <aliguori@us.ibm.com> wrote:
>>
>>> Thomas Han wrote:
>>> > Hi,
>>> >
>>> > For what it's worth. I have also seen this "invisible wall" problem
>>> > with my mouse for a few weeks off the CVS build too.
>>>
>>> Can you try out the following patch. *grumbles about SDL's brokenness*
>>>
>>> Regards,
>>>
>>> Anthony Liguori
>>
>>
>> --
>> Christian
>>
>>
>> _______________________________________________
>> Qemu-devel mailing list
>> Qemu-devel@nongnu.org
>> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
next prev parent reply other threads:[~2006-05-05 10:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 20:45 [Qemu-devel] QEMU 0.8.1 Fabrice Bellard
2006-05-03 21:00 ` Christian MICHON
2006-05-04 9:04 ` Mulyadi Santosa
2006-05-04 12:13 ` Christian MICHON
2006-05-04 12:24 ` Christian MICHON
2006-05-04 12:31 ` Christian MICHON
2006-05-04 13:14 ` WaxDragon
2006-05-04 14:51 ` Thomas Han
2006-05-05 2:31 ` Anthony Liguori
2006-05-05 6:57 ` Christian MICHON
2006-05-05 8:43 ` Natalia Portillo
2006-05-05 10:33 ` Oliver Gerlich [this message]
2006-05-05 11:33 ` Natalia Portillo
2006-05-08 17:35 ` Jim C. Brown
2006-05-05 14:08 ` Anthony Liguori
2006-05-05 14:23 ` Christian MICHON
2006-05-05 14:28 ` Anthony Liguori
2006-05-05 15:01 ` Christian MICHON
2006-05-05 15:57 ` Anthony Liguori
2006-05-08 17:40 ` Jim C. Brown
2006-05-08 20:12 ` Christian MICHON
2006-05-08 20:39 ` Brad Campbell
2006-05-08 21:05 ` Jim C. Brown
2006-05-09 23:18 ` Thomas Han
2006-05-10 9:30 ` [Qemu-devel] QEMU 0.8.1 - Invisible wall Dan Sandberg
2006-05-04 13:30 ` [Qemu-devel] QEMU 0.8.1 Chris Bagwell
2006-05-04 13:48 ` Christian MICHON
2006-05-05 1:56 ` Kazu
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=445B2A0B.7020501@gmx.de \
--to=olig9@gmx.de \
--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).