From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] GTK GUI for QEmu
Date: Fri, 11 Nov 2005 09:35:08 -0600 [thread overview]
Message-ID: <4374BA2C.2080702@codemonkey.ws> (raw)
In-Reply-To: <4373D8A1.5040203@gmx.de>
Oliver Gerlich wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>
>Hi,
>
>
Hi Oliver,
>just a short feedback on your qemu gui:
>
>
Appreciated :-)
>- -looks nice so far :)
>- -does it require a new(er) GTK? I only have 2.6.10 installed here, maybe
>that's why it doesn't find "GTK_STOCK_LEAVE_FULLSCREEN"
>
>
I'm using 2.8.6. I didn't realize that stock item was missing, I'll
include it in the next tarball for older versions of gtk.
>- -make install misses "camera.png"
>
>
Oops, sorry, I'll fix that too.
>- -the software scaler is maybe a good idea, but for fullscreen mode, I'd
>better like to have screen resolution switched to qemu guest resolution
>(as it is with normal qemu now)
>
>
I think a comprise may be the best solution. Perhaps switch to the
closest X resolution available and use software scaling to get you the
rest of the way there.
On at least one of my systems, I only have X set to use a single
resolution. I think that's common enough that it should be handled.
>- -sometimes the mouse can't be moved beyond some point on the guest
>screen... But I don't know when that happens and cannot really reproduce it
>
>
As Jim mentioned, this is a difficult thing to get right and I don't
currently try to work around it at all. The problem occurs when the
mouse hits the edge of the physical screen. The solution is most
certainly to warp the mouse back to the center of the screen when it
hits an edge.
FWIW, it's possible to reproduce this bug in the SDL version too.
>- -"mouse button up" events seem to be delayed somewhat: when clicking on
>an icon on the desktop of a Windows guest and releasing the mouse
>button, then dragging the mouse will drag the icon a bit
>
>
Interesting, I'll have to look into this.
>- -the windows key doesn't seem to work
>
>
I'll find a keyboard with a windows key and figure out the proper scancode.
>Apart from these (minor) glitches I quite liked the GUI. Btw. for the
>fullscreen mode you might want to have a look at the thread about Jim's
>GTK GUI - these issues have already been talked about there.
>
>
Thanks for the feedback!
Regards,
Anthony Liguori
>Oliver
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.1 (GNU/Linux)
>
>iD8DBQFDc9ifTFOM6DcNJ6cRAv+GAKCO2H5ygQZ/EaqONKEJlfcgeBUhYwCfSs3N
>1W4s9lCI2EijvwnptDQrkMM=
>=zEgy
>-----END PGP SIGNATURE-----
>
>
>_______________________________________________
>Qemu-devel mailing list
>Qemu-devel@nongnu.org
>http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
>
prev parent reply other threads:[~2005-11-11 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 22:07 [Qemu-devel] GTK GUI for QEmu Anthony Liguori
2005-11-10 23:32 ` Oliver Gerlich
2005-11-11 3:45 ` Jim C. Brown
2005-11-11 16:13 ` Oliver Gerlich
2005-11-11 18:55 ` Anthony Liguori
2005-11-11 19:30 ` Oliver Gerlich
2005-11-11 20:11 ` Jim C. Brown
2005-11-11 20:39 ` Anthony Liguori
2005-11-11 22:03 ` Jim C. Brown
2005-11-11 22:06 ` Anthony Liguori
2005-11-11 22:46 ` Jernej Simonèiè
2005-11-11 15:35 ` Anthony Liguori [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=4374BA2C.2080702@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).