From: Dan Sandberg <dan.sandberg@medsci.uu.se>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU 0.8.1 - Invisible wall
Date: Wed, 10 May 2006 11:30:45 +0200 [thread overview]
Message-ID: <4461B2C5.7060005@medsci.uu.se> (raw)
In-Reply-To: <170581c20605091618k18f2617ajd4ff14b7ffa353fc@mail.gmail.com>
Thomas Han wrote:
> Hi Anthony,
>
> Sorry for the late reply. I did try out the patch with my local build
> and I
> haven't see that "invisible wall" mouse problem for a few days now.
>
> Thanks very much,
> Thomas
>
> On 5/4/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
>>
>> > Since 0.8.1 came out yesterday, Instead of using CVS build, I'm now
>> > running Qemu 0.8.1 + kqemu-1.3.0pre6. My host OS is FC5 and I'm
>> > running XP inside it.
>> >
>> > Thanks,
>> > Thomas
>> >
>> > On 5/4/06, *Christian MICHON* < christian.michon@gmail.com
>> > <mailto:christian.michon@gmail.com>> wrote:
>> >
>> > qemu 0.8.0 does not show this invisible barrier issue.
>> > if this is worth anything, I use SDL 1.2.9.
>> >
>> > If someone can reproduce the issue also on linux hosts,
>> > there could be a lead.
>> >
>> > On 5/4/06, Christian MICHON <christian.michon@gmail.com
>> > <mailto:christian.michon@gmail.com>> wrote:
>> > > I removed manually vnc_display_init, and this is not the
>> culprit...
>> > > I'll check anyway versus qemu-0.8.0...
>> > >
>> > --
>> > Christian
>> >
>> >
>> > _______________________________________________
>> > Qemu-devel mailing list
>> > Qemu-devel@nongnu.org <mailto: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
>> >
>>
>>
>>
>> diff -r 39a6dd1136c6 sdl.c
>> --- a/sdl.c Thu May 04 04:13:13 2006 +0000
>> +++ b/sdl.c Thu May 04 21:30:11 2006 -0500
>> @@ -280,13 +280,18 @@ static void sdl_update_caption(void)
>>
>> static void sdl_hide_cursor(void)
>> {
>> - SDL_SetCursor(sdl_cursor_hidden);
>> + if (kbd_mouse_is_absolute()) {
>> + SDL_ShowCursor(1);
>> + SDL_SetCursor(sdl_cursor_hidden);
>> + } else {
>> + SDL_ShowCursor(0);
>> + }
>> }
>>
>> static void sdl_show_cursor(void)
>> {
>> if (!kbd_mouse_is_absolute()) {
>> - SDL_SetCursor(sdl_cursor_normal);
>> + SDL_ShowCursor(1);
>> }
>> }
>>
>>
>>
>> _______________________________________________
>> 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
>
>
On my installation (v0.8.1 with WindowsXP host) the "invisible wall" can
be avoided or reproduced at will and I guess this indicates what´s wrong.
After leaving MouseGrab with Ctrl-Alt there will be an invisible wall if
I reenter by clicking with the host's mouse pointer far away from where
the quest-OS-pointer is. On the other hand if I reenter by carefully
clicking exactly at the guest-OS-pointer they will be in sync and
everything seems to be OK.
I haven´t been looking at the source-code, but my suggestion is that in
the Click-event-handler where Mousegrab is entered the guest-OS pointer
coordinates should be passed rather than the host's coordinates
(simulating a click at the exakt right position).
Regards
Dan Sandberg
next prev parent reply other threads:[~2006-05-10 9:56 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
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 ` Dan Sandberg [this message]
2006-05-04 13:30 ` 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=4461B2C5.7060005@medsci.uu.se \
--to=dan.sandberg@medsci.uu.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.