qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] gtk2 driver
Date: Mon, 30 May 2005 19:03:06 -0400	[thread overview]
Message-ID: <20050530230306.GA5498@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <429B8142.40902@bellard.org>

On Mon, May 30, 2005 at 11:10:26PM +0200, Fabrice Bellard wrote:
> >>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.
> >
> >
> 
> If GTK cannot support correct full screen output, then it is perfectly 
> acceptable to do direct X11 calls thru DGA/Xvidmode for example.
> 
> Fabrice.
> 
> >This is also doable, but it is less portable (e.g. it wouldnt work on 
> >Windows).
> >

Ok this is what I've decided to do. In order to ensure that gtk2.c will work on
windows, I have decided to keep the fullscreen code separate.

There will be a fullscreen.h that defines the 4 functions that gtk2.c depends
on, and there will be a fullscreen "driver" of the name <library>_fs.c that
implements these functions.

I've written an xvid_fs.c which implements fullscreen mode via the Xvidmode
extension as well as a null_fs.c which doesn't do anything.

This way, Linux/FreeBSD/etc users can use the xvid_fs driver to get fullscreen
mode with gtk and Windows users can use the null_fs driver to use gtk mode.

The idea is that someone could implement a win32_fs driver that would enable
fullscreen mode in Windows. I do not know enough about win32api programming to
write this myself.

If gtk mode is enabled, the configure script will select the correct driver
by default (xvid_fs on unix, null_fs for everyone else) but there will be an
option to override this.

I have a few kinks to work out (plus some configure/Makefile diffs to write)
but expect a patch and the new files in a few hours.

On a side note, has anyone tried to use the gtk2 driver on windows? If so, can
you tell me what happened?

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2005-05-30 23:22 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
2005-05-30 23:03       ` Jim C. Brown [this message]
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=20050530230306.GA5498@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).