On 3/30/07, Alex Holkner <[EMAIL PROTECTED]> wrote: > > > Wouter van Heyst wrote: > > > > > > > On 3/30/07, *Alex Holkner* <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > > Wouter van Heyst wrote: > > > > > Hey all, > > > > > > has anyone tried to use pyglet to do the work on an OpenGL > > widget (in > > > my case currently for wx?) > > > I'm hoping it's mostly a case of telling pyglet what context to > > use, > > > but perhaps there is more work that needs to be done. > > > > If your widget already creates a context, then pyglet will work > right > > now: just switch to the context (in the other framework), and start > > using pyglet.gl <http://pyglet.gl> functions. You would not use > > pyglet.window at all in > > this scenario. > > > > > > My problem was pyglet.font needing a shared space, and assuming there > > was a window available. > > This is only an issue if you're using multiple contexts which don't > share their objects. You could create a dummy window (so long as it's > created with visible=False, no context will be created), switch to the > real context, and Font will be happy.
A cleaner solution than my sys.modules['shared_space'] = FakeObjectSpace() ;) Thanks. Wouter van Heyst --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
