On Fri, Apr 29, 2011 at 12:02 PM, Zachrahan <[email protected]> wrote:
> Talking to myself here, but for the benefit of others who might > wonder: it appears from googling that cocoa GUIs have to be run from > thread-0; not so for carbon GUIs. This seems to be an OS/cocoa-level > limitation. > If memory serves, the restriction isn't that everything has to run from thread zero, just that it all has to run from the same thread where the NSApplication is spawned. > My initial email still reports a relevant bug in the cocoa backend in > that "import pyglet.app" starts some GUI code running, whereas for > other backends nothing happens until the event loop is explicitly > started... I don't quite understand what you mean here, and I think it might be related to a misunderstanding about how Cocoa operates. You want to be able to create a pyglet window before starting the event loop, right? Well a window is a GUI resource, so the GUI framework must be initialised by this time (i.e. as soon as you import pyglet). And initialising AppKit involves creating the NSApplication instance, which will cause the dock icon and menu bars to be created. -- Tristam MacDonald System Administrator, Suffolk University Math & CS Department http://swiftcoder.wordpress.com/ -- 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.
