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.
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... On Apr 29, 11:53 am, Zachrahan <[email protected]> wrote: > OK, here's an even easier test case. On a completely un-modified > pyglet 1.2, the following works fine with carbon (dock icon appears > and then stops bouncing, app's menu bar is responsive) but not with > cocoa (bounces forever and app beachballs): > > def start_pyglet(): > import pyglet.app > pyglet.app.event_loop.run() > > import threading > t = threading.Thread(target=start_pyglet) > t.setDaemon(True) > t.start() > > Anyone have any ideas whatsoever? -- 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.
