From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] gtk2 driver
Date: Mon, 30 May 2005 16:21:07 -0400 [thread overview]
Message-ID: <20050530202107.GA3663@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <20050530211042.A17280@bbland>
On Mon, May 30, 2005 at 09:10:43PM +0200, Lionel Ulmer wrote:
> On Mon, May 30, 2005 at 01:11:09PM -0400, Jim C. Brown wrote:
> > Fullscreen mode is still broken (the window will resize, but the image on the
> > window will not). This will be tricky to fix as software scaling will be
> > necessary to get the image to be the right size/shape. Unlike SDL or OpenGL,
> > which could alter the video resolution of the X server. Perhaps the best
> > solution is to use an embedded GTK GLX widget to render the image. What do
> > you think Fabrice?
>
> Why not switch to SDL output when the user requests going 'full-screen' ? It
> would be a bit of a hack, but well, it could work :-)
>
It's a very easy hack to write, and it wouldnt be very difficult to get to work.
There is a gtksdl widget for gtk2 that I could use just for this purpose -
that way you could still have say a drop down menubar to use (for the GUI).
Or the gtk code could simply call upon the SDL driver when it goes into
fullscreen mode.
> Otherwise, just use plain X11 calls to change resolution (via XRandr or via
> Xvidmode). The problem being always to properly 'align' this window to be
> the only one on screen.
This is also doable, but it is less portable (e.g. it wouldnt work on Windows).
Either of these approaches mean moving away from pure GTK/GDK. Fabrice hasn't
explained why, but he has made it clear that he wants the Linux to use GTK.
Also, I'd prefer not to use X11 in the gtk driver in the hopes of keeping it
Windows compatible.
>
> Lionel
>
> --
> Lionel Ulmer - http://www.bbrox.org/
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-05-30 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 17:11 [Qemu-devel] gtk2 driver Jim C. Brown
2005-05-30 19:10 ` Lionel Ulmer
2005-05-30 20:21 ` Jim C. Brown [this message]
2005-05-30 21:10 ` Fabrice Bellard
2005-05-30 23:03 ` Jim C. Brown
2005-05-31 0:24 ` Jim C. Brown
2005-05-31 14:15 ` Sylvain Petreolle
2005-05-31 18:54 ` Jim C. Brown
2005-05-31 19:45 ` Jim C. Brown
2005-05-31 20:28 ` Jim C. Brown
2005-05-31 23:44 ` Jim C. Brown
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 11:42 [Qemu-devel] [PATCH] Embed QEmu screen on a custom window Miguel Angel Fraile
2005-05-26 12:10 ` Christian MICHON
2005-05-26 20:03 ` Fabrice Bellard
2005-05-26 20:32 ` gtk [was Re: [Qemu-devel] [PATCH] Embed QEmu screen on a custom window] Jim C. Brown
2005-05-27 6:07 ` Jim C. Brown
2005-05-27 10:59 ` [Qemu-devel] gtk2 driver Sebastien Bechet
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=20050530202107.GA3663@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--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).