On Sat, May 2, 2009 at 12:52 AM, Padraig Kitterick <[email protected]> wrote: > 1) Why does pyglet draw at 60fps, regardless of whether I use > clock.set_fps_limit() ?
set_fps_limit() is deprecated, and not expected to work with the new-style event loop. Nothing in pyglet forces a 60fps framerate. By default, scheduled clock functions (including using ClockDisplay) and events will cause the window to repaint. > 2) Why does pyglet flip() the window buffers when _any_ event happens by > default, even when that event doesn't alter the buffers? This behavior means > that scheduling any function to be called at short intervals will push the > fps to the maximum of 60, regardless of what that function is doing, i.e. > whether it has an effect on the buffers or not. Not a criticism, just > curious... This is the easiest development model for an application/game developer (it avoids bugs in which the developer forgets to invalidate the window). The WIndow.invalid flag exists as an opt-in way to tell pyglet not to redraw the window by default, if you want to manage invalidating the window yourself. 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 -~----------~----~----~----~------~----~------~--~---
