Actually, you could combine these ideas, and use the custom clock to only call rabbyt.add_time. Basically the custom clock would be a rabbyt clock.
On Jul 18, 12:00 pm, Keeyai <[EMAIL PROTECTED]> wrote: > I think the custom clock mentioned by diordna is a great place to > start and is probably the 'right' way to do it. > > A little bit more hackish would be to only schedule your game events > with the rabbyt scheduler, then stop calling rabbyt.add_time. Pausing > like this is even mentioned in the > docs.http://matthewmarshall.org/projects/rabbyt/docs/rabbyt/anims/ > > This approach is probably confusing to others reading your code, but > gives you a way to split up your game clock and the low level pylet > clock. Still, I would go with the custom clock option from above for > clarity and style. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
