I didn't expect it to work without a few changes. I simplified the entire implementation and likely broke a few things. For one, I didn't like that the scheduler was tightly coupled to the system clock and event loop. My implementation is more generic. At this point, I think the easiest way to adapt it would be to use this version, then add the missing bits. It's also written for Python 3.4, so there may be some parts that won't work with 2.7.
I never pushed for inclusion in pyglet mostly because I didn't want to back port it and wasn't sure if it was needed. Guess I was wrong. I'll let this issue sit for a few days then consider merging it if I get more response. There needs to be more testing than just my own use though. It has the potential for making odd bugs due and that's scary. Anyway, I'll revisit this next week after some thought. -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
