On 25/03/13 17:23, Peter B wrote:
Pyglet 1.2 alpha DEFINITELY broke the scheduling. I see people asking
the same thing, why the clock.set_fps_limit which previously worked is
now no longer working as advertised, and the response seems to be Oh,
just don't use it, and schedule everything on time intervals. Which is
fine unless you WANT sometime to fire each frame.
I'd appreciate some explanation of why this happened.
pyglet.clock.set_fps_limit is deprecated
http://pyglet.org/doc/api/pyglet.clock-module.html#set_fps_limit
If you want something to happen every frame possible then use
pyglet.clock.schedule with your update function as was mentioned earlier
in this thread. If you want to restrict the frame rate the correct way
to do that now is to use schedule_interval and a redraw will occur when
that happens assuming your monitor refresh rate is faster than the interval.
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
