On Fri, Apr 25, 2008 at 8:02 AM, selsine <[EMAIL PROTECTED]> wrote:
>
>  Hi Alex,
>
>  On Apr 24, 8:47 am, "Alex Holkner" <[EMAIL PROTECTED]> wrote:
>
> > On 4/24/08, selsine <[EMAIL PROTECTED]> wrote:
>  >
>  >
>  >
>  > >  Hi Alex,
>  >
>  > >  I went back through the revisions and found that I started to get the
>  > >  white boxes after revision: 2008.
>  >
>  > >  So revision 2007 and before work, and 2008 and later give me the white
>  > >  boxes.
>  >
>  > >  I hope that helps. If you need me to test anything let me know.
>  >
>  > That change was in the way modules are loaded lazily.  Make sure that
>  > before loading any images or doing any rendering you switch to GTK's
>  > context.
>
>  I thought it might be something like that, but because other images
>  worked after I sort of wrote that reason off. What did the change from
>  r2007 to r2008 mean? I'm just trying to get a better idea of what is
>  happened so that I can update my code.

In r2007 and earlier, the pyglet module was replaced with a class
instance which performed the lazy importing.  This was causing some
havoc with import-time exceptions though (probably a bug in Python),
so as of r2008 the module is untouched, and proxy objects are used for
lazy imports.  Examining the source code should make this clear.

This may have affected the order in which modules are imported in some
situations (and so when the shadow GL context is first created).
>  > >  I've also noticed that the current set of examples included with the
>  > >  1.1beta won't quit on my system. I went back and looked at the
>  > >  image_view.py example. It seems that this stopped closing using the
>  > >  close button (the X) on the window in revision 1920. Revision 1919
>  > >  works fine on my system, all revisions past that need for be forcibly
>  > >  closed.
>  >
>  > I can't reproduce this, can you post the output of `python -m pyglet.info`?
>
>  Here you are:

I can't reproduce it on my Linux computer either.  Check that
pyglet.window.xlib.XlibWindow._event_clientmessage is correctly
receiving the event from your window manager, and then perhaps trace
the execution of the on_close dispatch to find out why the window's
not closing.

Alex.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To post to this group, send email to pyglet-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to