Probably not. That sounds like the shared code issue described in the modules preso on my blog (blogs.adobe.com/aharui)
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of ninja_gerbils Sent: Monday, February 18, 2008 9:25 AM To: [email protected] Subject: [flexcoders] trouble passing events between modules I have a basic module-loading framework. Basically, some javascript calls specify which modules to load; they are then loaded into a tabnavigator. I also have an library with a couple of different events in it, as well as a singleton EventDispatcher. I want to use these events to pass data between various modules. I use the singleton instance of this dispatcher both to add event listeners in some of the modules, as well as to dispatch events in the other modules. The problem is that the events are not crossing from module to module. I can receive the events in the module that dispatched them, but not in any others. As a debugging test, I added an event handler for the event in question in my parent framework app, and all of a sudden everything started working. With more testing, I've found I can get any event from my library to go from module to module, but only if I add a (blank) handler for that event in my framework app. This seems very wrong; is there something I'm missing?
