Yes. As I said in the other post, my confusion was not understanding the relationship between the bubbling mechanism and the UI display list.
I changed it back to extending EventDispatcher and dispatching off the main app object. All is well. --- In flexcoders@yahoogroups.com, "Manish Jethani" <manish.jeth...@...> wrote: > > On Mon, Jan 12, 2009 at 8:59 PM, biosmonkey <biosmon...@...> wrote: > > > The dispatched event needs to be heard by any component, anywhere, by > > setting an event listener for it at the application level. So > > bubbling up to the app is critical. > > Since your component has nothing to do with UI, strictly speaking, > making it a UI component (extending DisplayObject) seems like the > wrong thing to do. Event bubbling is typically for UI events; your > event is not a UI event, it's just that you need it to be broadcast > application-wide. > > So I would consider making the event dispatcher object available > application-wide, by making it a singleton, for instance, or by making > it a property of the main application. It seems you're already doing > something to that effect -- dispatching off the main application > object. > > Manish >
