From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] gtk2 driver
Date: Mon, 30 May 2005 23:10:26 +0200 [thread overview]
Message-ID: <429B8142.40902@bellard.org> (raw)
In-Reply-To: <20050530202107.GA3663@jbrown.mylinuxbox.org>
>>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.
If GTK cannot support correct full screen output, then it is perfectly
acceptable to do direct X11 calls thru DGA/Xvidmode for example. Using
SDL for full screen is possible too, but I think it will be a source of
problems (see the keyboard bugs we have with SDL/Windows).
Fabrice.
next prev parent reply other threads:[~2005-05-30 21:14 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
2005-05-30 21:10 ` Fabrice Bellard [this message]
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=429B8142.40902@bellard.org \
--to=fabrice@bellard.org \
--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).