From: "andrzej zaborowski" <balrog@zabor.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Guest mouse cursor drawing in SDL
Date: Mon, 26 Mar 2007 22:30:36 +0200 [thread overview]
Message-ID: <fb249edb0703261330s7c84b617j50c124f907e2ea34@mail.gmail.com> (raw)
In-Reply-To: <46070AA3.5080002@codemonkey.ws>
Hi,
On 26/03/07, Anthony Liguori <anthony@codemonkey.ws> wrote:
> andrzej zaborowski wrote:
> > Hi, sorry for late reply.
> >
> > On 21/03/07, Anthony Liguori <anthony@codemonkey.ws> wrote:
> >> Do you think using the SDL cursor is all that useful? As soon as gtk
> >> widgets get involved, the cursor becomes ARGB so in practice, I'm not
> >> sure that it's all that helpful.
> >
> > It's pretty cool that you have only one cursor and that it's either
> > "in the VM" or outside, and it's full hardware drawn. In addition
> > without it, I think you can't get cursor refreshes between the SDL
> > refresh callbacks. So with the patch the cursor movement is really
> > smooth and responsive, eliminating the SDL latency. I find it amazing
> > that it works :p
>
> Hrm, interesting. I actually want to rethink the mouse interface again
> as I've been thinking that even if an absolute mouse isn't available,
> provided that you know the location of the guest cursor, you can
> implement a smarter grab/ungrab.
I was thinking about this too but the issue is with grabbing.
Ungrabbing is straight forward, but when you grab, you will need to
either move the host cursor to the location of guest cursor or the
other way (which would be some iterative converging algorithm).
>
> > I think VNC support is not a reason to drop this couple of lines in
> > sdl.c (cause there's no API changes related).
> >
> >>
> >> BTW, I've got the ALPHA_CURSOR working with VNC.. it's very sweet :-)
> >
> > Awesome! Are there screenshots?
>
> I could make them, but they just show a mouse in the window :-) BTW,
> have you thought about how to integrate std-vga into the vmware vga
> device? I took a look at it and it seems like it will be overly
> complicated based on the way VGA memory dirtying is done now.
Yeah, it will require changes in hw/vga.c but it doesn't look very
difficult or hacky.
Regards,
Andrew
prev parent reply other threads:[~2007-03-26 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 14:19 [Qemu-devel] [PATCH] Guest mouse cursor drawing in SDL andrzej zaborowski
2007-03-20 15:08 ` Thiemo Seufer
2007-03-20 15:38 ` Anthony Liguori
2007-03-20 16:06 ` andrzej zaborowski
2007-03-21 1:28 ` Anthony Liguori
2007-03-23 13:57 ` andrzej zaborowski
2007-03-25 23:49 ` Anthony Liguori
2007-03-26 20:30 ` andrzej zaborowski [this message]
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=fb249edb0703261330s7c84b617j50c124f907e2ea34@mail.gmail.com \
--to=balrog@zabor.org \
--cc=anthony@codemonkey.ws \
--cc=balrogg@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).