I would have to agree with Alex on this one. The clock in pyglet is not meant to be a real-time, high-resolution timer. It is only meant to be a convenient way to execute functions at a later time in a casual programming situation, much like the setTimeout and setInterval functions in JavaScript. The documentation is pretty clear about that. If you absolutely need a highly accurate timer, you're on your own on that one.
When you're checking for a margin of error on every call of clock.tick, that's a giveaway that you're thinking about pyglet.clock the wrong way. Is there any particular reason why you need these functions executed within a very specific amount of time? Or are you just over-engineering for the fun of it? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
