At the moment, ClockDisplay objects schedule themselves on the default clock in their initializers, but provide no facility for unscheduling. This means that ClockDisplay objects hang around forever, even after they've gone out of scope. This behaviour is mentioned nowhere in the documentation, and can cause huge slowdown if ClockDisplay objects are being regularly created.
Obviously, one can work around this by calling cd.clock.unschedule(cd.update_text) when the ClockDisplay is no longer required, but this seems hacky. A __del__ method seems like the obvious way of solving things, but unfortunately the clock keeps a reference to the scheduled method, so this doesn't work. Anyone have any ideas for a better solution? martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
