Ah, nice find. Shouldn't be too hard to fix. Hopefully we can do it in a way that doesn't impact performance too much, but I suppose that unscheduling isn't a super performance critical thing, but it's nice to keep the clock as fast as we can.
Leif actually wrote this heap based clock a short while ago, which was a nice improvement. This is new in 1.3, so it's nice to find bugs like this. -- 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 https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
