On Tue, Mar 25, 2008 at 2:24 PM, Nathan <[EMAIL PROTECTED]> wrote: > > Oookay, gmail hates me tonight and decided to send while I was typing. > Let's try that again: > > > > So, related to my last post, I'm reading the 1.0->1.1 migration docs, > > and am trying to see if using pyglet.app.run() will somehow make > > twisted and pyglet play nicely again...but I can't figure out how to > > integrate pyglet.app.run() in! > > > > Before, I was subclassing a window, and coiterating a run() method on > > the window object, like this: > > class MyWindow(window.Window): > def run(self): > while not self.has_exit: > > do_some_stuff_like_dispatching_updating_and_drawing() > yield 1 > > my_window = MyWindow() > task.coiterate(my_window.run()) > reactor.run() > > > But pyglet.app.run() isn't a tight loop that yields. Suggestions?
The programming guide has some detail on hooking into the app loop. You won't be able to use it concurrently, but there is probably another way to hook twisted in. You can also continue to use the old dispatch_events method. If there's a regression, post a test case (preferably one without twisted) so I can debug it. Alex. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
