Snipplr comments feed https://snipplr.com/ Sun, 19 Apr 2026 06:40:38 +0000 https://snipplr.com/view/6650/messager-pattern-from-panda3d <p><p></p></p> Wed, 11 Jun 2008 19:07:39 UTC https://snipplr.com/view/6650/messager-pattern-from-panda3d https://snipplr.com/view/6650/messager-pattern-from-panda3d <p><p></p></p> Wed, 11 Jun 2008 19:08:14 UTC https://snipplr.com/view/6650/messager-pattern-from-panda3d https://snipplr.com/view/6650/messager-pattern-from-panda3d <p><p>Zero|Byte showed me an alternative version of this that. Instead of mapping strings to (function, accepter<em>argument, sender</em>argument) tuples his maps class names to to functions: http://dpaste.com/56722/</p> <p>When you call messager.send(...) you pass either an event class (and messager will create a new instance for you_ or an instance of an event class, message finds all functions subscribed to that class name and calls them, passing the event class as the single argument. The idea is that you create different event classes and the receiver functions use their attributes as arguments. Nice. His version doesn't allow you to give an argument when you call accept(...), but I've never found much use for that anyway. I like it.</p></p> Sun, 15 Jun 2008 13:40:02 UTC https://snipplr.com/view/6650/messager-pattern-from-panda3d