On Sat, May 2, 2009 at 7:46 AM, Alex Holkner <[email protected]> wrote:
> > No, but IIRC there is no need to set invalid = False in the scheduled > clock function, as this happens always. Perhaps you have some other > scheduled events that you didn't intend to repaint the window? (If so, > then you can consider this a feature limitation or bug in pyglet). > > I do seem to have to set the invalid flag in the update method, or the window doesn't refresh at all. However, this results in a very variable framerate even without events - where as the standard event loop is only variable when events occur. I guess the best solution is probably to override the default event loop, but it seems as if it should be simpler. -- Tristam MacDonald 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 -~----------~----~----~----~------~----~------~--~---
