simpsus_science wrote: > 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.
You know, it's not all that hard to write your own scheduler that does things the way you want. The one in Rabbyt is only 10 lines of code or so. MWM --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
