Quote Originally Posted by ZorbaTHut View Post
Three quick responses: * There's no reason whatsoever that you should feel obliged to stick with Rift's event system. We're providing easy tools if you want to do so, but if you prefer some other event layout, go for it! Utility.Dispatch() even allows you to credit CPU time off to other addons as you see fit. * You can always put "event name" as a first parameter to an event, then have events check that name when the event fires. The downside is that of course now you're doing a traversal over every possible event handler each time one event fires. * If you want to get totally crazy, you can always do some craziness behind the scenes and add a metatable in the event tree that transparently creates new event handler tables as they're requested. I don't recommend doing this on top of an actual event that's been created, but the event hierarchy itself is just plain ol' Lua tables for organization.
Jump to post...