Well, going to the basic, why do we need an event, when we are going down into the children.
It is wise to use events, when you need to notify some change in the children to the parent or up in the hierarchy. My suggestion will be just expose a public function in the module, which can internally do the desired task with respect to the module. In main application, just decide your currently loaded module and invoke the function blindly, when needed. You can also make use of interface at this point to make it more standardize. On Tue, Oct 6, 2009 at 1:12 PM, zxcvb <[email protected]> wrote: > > I found this but it doesn't seem to work for me: > > http://yakovfain.javadevelopersjournal.com/flex_best_practices_sketch_1_an_application_with_a_single_.htm > > I urgently need to come up with a solution to pass an event to a > module from an application. > > The modules pop up titlewindows which close when the user clicks > somewhere in the module. > > Unfortunately, I just found out that the titlewindow doesn't close > when the module is unloaded. > > I think I need to send an event to the module to close it. But that > isn't working: > > mdLoader.child.dispatchEvent(new CloseEvent(CloseEvent.CLOSE, true)); > > Please help. It's very urgent. > > > > -- Thanks, Vaibhav Seth. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex India Community" group. 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/flex_india?hl=en -~----------~----~----~----~------~----~------~--~---
