On Aug 25, 7:44 pm, Richard Thomas <[email protected]> wrote:
> The set_fps_limit function I have never understood, it has no
> discernable effect.
The 1.1 docs have this to say, in 'Appendix: Migrating to pyglet 1.1'
"Update functions can be scheduled on the clock. To have an update
function be called as often as possible, use clock.schedule (this
effectively degenerates into the older dispatch_events practice of
thrashing the CPU):
def update(dt):
pass
clock.schedule(update)
Usually applications can update at a less frequent interval. For
example, a game that is designed to run at 60Hz can use
clock.schedule_interval:
def update(dt):
pass
clock.schedule_interval(update, 1/60.0)
This also removes the need for clock.set_fps_limit."
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
