On May 11, 1:24 pm, Tristam MacDonald <[email protected]> wrote: > > This is interesting. What do I do if I need an event loop for a pyglet > > OpenGL window and another one for other UI elements (e.g. wx > > windows)? It seems that pyglet quickly breaks when it's not on the > > main thread, and wx does as well - how can I run these two together? > > I would recommend dumping the pyglet window entirely, and just using a > wxWindow with a wxGL context to render. > > However, if you really want the separate windows, you can try just getting > rid of the pyglet event loop, and manually calling window.dispatch_events() > and window.flip() instead.
I'll give this a shot and hopefully let you know whether it worked or not. > > > FWIW, > > things work fine with a secondary thread for the wx window on Ubuntu > > and Windows. > > Mac is special - and not always in a good way. I think it is at least partly > because the entire UI is drawn using OpenGL, but whatever the reason, native > UI elements (and by extension wxWidgets) are a bit tricky to manage on a > separate thread from your OpenGL rendering. Shucks. Thanks for the info! Matt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
