On Fri, 11 Apr 2008, Zachrahan wrote:
> (2) Moreover, it seems that for pyglet 1.1a2, ANY import statements
> for pyglet ('import pyglet.window', or even 'import pyglet') must be
> done in the context of the thread which will be handling the windows.
> ...
> I don't know if this is properly a "bug" in pyglet 1.1a2, but it
> certainly is an oddity in how it operates and a definite gotcha.
It's an unfortunate side-effect of the import-pyglet-side-effect (and one
reason why there's a general rule that import statements shouldn't have
side-effects) that a context is created at first import. This is done for
convenience, but I'm becoming increasingly uneasy with it (and sorry I forgot
to bring this up yesterday, Alex :)
Richard
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
