Hello all, First, thanks to everyone who's worked on the cocoa pyglet version. This is really fantastic.
A while ago, I hacked up some code to run a pyglet event loop in a background thread, so one can have an interactive python interpreter going at the same time as pyglet windows. This all works fine as far as the OS and GL etc are concerned (at least on mac carbon and windows), so long as all the GUI calls are made from the same background thread. I'm having trouble getting this working with cocoa, however. (It seems to work with pyglet 1.2 and carbon when I run in 32-bit mode though.) Basically, it seems that, even with the "shadow_window" option off, importing pyglet.app causes some GUI code to execute (you can tell because an icon starts bouncing in the dock then). It appears to be the calls in pyglet.app.cocoa.CocoaEventLoop.__init__() that do this, starting with: NSApplication.sharedApplication() Is it possible/safe to defer these until the event loop is started? This is how things appear to work in carbon and on windows... Also, while on the topic -- I see that a lot about thread-safety has gone into pyglet 1.2, but I'm not sure what the use-cases are for that... does this have any impact on what I'm trying to do here? Thanks, Zach -- 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.
