Glad to channel Alex Harui's old posts, since I've been using it since he wrote it.
By the way, the same thing works well in an MDIWindow setup as well. But that only helps if you are using FlexMDI in FlexLib http://code.google.com/p/flexlib/ --- In [email protected], "hr1ny" <[EMAIL PROTECTED]> wrote: > > Thanks! That is just what I needed. > --Henry > > --- In [email protected], "actionscript_czar" <daryl@> > wrote: > > > > Alex would probably be recommending extending TitleWindow in a way > > that allows you to use it as a top level module. > > > > See this: http://blogs.adobe.com/aharui/2007/08/ > > popup_dialogs_as_modules.html > > > > --- In [email protected], "hr1ny" <hrabinowitz@> wrote: > > > > > > Gregor, > > > Thanks for your post. I agree with you that Alex's blog contains > > the > > > relevant info. I did move the popup module's Event classes into > > the > > > parent app, and the problem of Type Coercion goes away (though I'd > > > rather find a solution that did not require this). But one other > > > aspect of Alex's recommendation mystifies me. > > > > > > He recommends putting the TitleWindow inside the Module, like > this: > > > > > > <mx:Module> > > > <mx:TitleWindow> > > > ... > > > </mx:TitleWindow> > > > </mx:Module> > > > > > > > > > but if I do this, and use PopUpManager.addPopUp() to raise this > > > object, it is not draggable. > > > I think to have a draggable popup window, it needs to inherit from > > > TitleWindow. Yet that approach is the one he disparaged. So I'm > > not > > > sure how to resolve it. > > > --Henry R. > > >
