Hi, thanks that this patch is appreciated. I would like to point out one thing: I have already committed a patch to our AWT demo application to test this GraphicsDevice stuff. You can change the display mode and try out fullscreen exclusive mode (which isnt real FSEM but the disable window decorations and maximize thing).
I would like to see that people try this code on their machines to find out whether it works with other windows managers, XOrg/XFree versions and operating systems. Please report any issues to gcc.gnu.org/bugzilla. Btw: The functionality is now only implemented for the Gtk peers. We need the same stuff for the Qt ones. I do not have access to such a system and not much time to work on that but it is possible that this would not be so difficult as one can reuse the X11 code in the Gtk version. Anyone lurking on this list and looking for a low hanging fruit: Go for PR27927 !!! :) Happy hacking! cya Robert [0] - http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27927 Sven de Marothy wrote: > On Tue, 2006-06-06 at 12:02 +0200, Robert Schuster wrote: > >>Hi, >>this patch implements the GdkScreenGraphicsDevice and related classes. > > > Great! Now we can fill in the missing puzzle piece for VolatileImage, > which is the GraphicsEnvironment constructor. It should probably take a > GdkScreenGraphicsDevice as a parameter. > > The reason for this is that VolatileImage wraps an X pixmap both in our > impl and in the JDK (says Sun's docs), and to create a pixmap you need > to know the native screen parameters. Which can be recieved either from > an existing widget (GtkComponentPeer constructor -implemented.) or from > a GdkScreen (not implemented). > > So you should all understand now why the createVolatileImage methods > happen to be in GraphicsConfiguration and Component. :) > > /Sven > > >
signature.asc
Description: OpenPGP digital signature
