On Tuesday, September 4, 2012 1:24:51 AM UTC-4, Nathan wrote:
> By the way, you can already remove handler(s) from the middle of the > stack, providing you know exactly what callable was pushed onto it: > > > http://pyglet.org/doc/api/pyglet.event.EventDispatcher-class.html#remove_handler > This is not *quite* the same, since it leaves the frame, and you now have an empty frame you have to keep track of and double-pop later > Every time I've found myself wishing for similar modifications to pyglet's > event design, I soon found that conforming to the existing design forced me > to improve my own code's structure quite a bit. I do feel like I'm getting hit by this the more I think about it. It may be that I'm using pyglet's event system in a way it wasn't intended, or to a degree it wasn't intended. -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To view this discussion on the web visit https://groups.google.com/d/msg/pyglet-users/-/IlU5_KasYiYJ. 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.
