what is a showstopper for me is that rabbyts scheduler does not support unscheduling in contrast to pyglets scheduler. pyglet has a glitch to that because pyglets scheduler passes the dt time to the called function, which is a problem is you schedule lambda dt: call() because you cannot unschedule that (unless you store it). But thats just a sidenote (I wrote abount it in another thread).
Anyway, to keep my app sane I need to unschedule things from time to time, so using rabbyts scheduler is not an option. But thanks for the masses of replies! Especially diordna's class seems very promising. I will definetely try that! Although I kind of wonder: Why isn't this functionality already inside the default pyglet clock? Am I the only one who wants to pause his game? And to me pausing seems to be something that global that it would easily fit in a standard clock. Thanks again. Your help is much appreciated! Cheers Bastian On Jul 18, 11:14 pm, infinite8s <[EMAIL PROTECTED]> wrote: > 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. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
