Why don't you just add an event listener in your parent. Then all your popup has to do is dispatch the event. You can even pass data in the event.
Checkout addEventListener for the parent Checkout dispatchEvent for the popup --- In [email protected], "charlespaz1" <[EMAIL PROTECTED]> wrote: > What I'm looking for is a user verification window, like when deleting > a record, it shouldn't be done lightly, so I want a popup to appear > asking "Are you sure" then the listener returns the results. If they > choose yes, then continue execution, otherwise, don't. > > Now I could add the code to check in the handler, but I want the popup > to be more versitile, so what I want to do (if possible) is to open > popup, handler gets results on popup close, then, based on results, > perform a specified action. > > If it isn't possible, I will have to have 3 different popups with 3 > handlers for three different actions, which is what I'm trying to avoid. > > --- In [email protected], "Rob Rusher" <[EMAIL PROTECTED]> wrote: > > Don't think procedural. Think broadcast/listener. > > > > If you're waiting on service results, just add setBusyCursor="true" > to the > > service component. This will prevent the user from doing anything > until the > > results return. Then in your results handler, close the popup. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
