On 30/11/2007, sol <[EMAIL PROTECTED]> wrote: Is this expected behavior? Should the Clock do one tick() when it is > created automatically?
I would say that what you are experiencing is expected behaviour, ie, the clock won't tick until you tell it to, therefore nothing will be scheduled until the clock has ticked. The docstring for the tick() method says, "This will call any scheduled functions that have elapsed." Looking at the code for tick(), it looks at the current time, invokes the functions that are scheduled for every frame (with the implication that you should only call tick() once per frame), then loops through a list of functions sorted by time, invoking those functions whose schedule time is less than or equal to the current time. --- Rod --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
