Thanks Igor, I tried this, but creationComplete executes as well...really weird :? But if I instantiated the component directly the creationComplete does not exectute, so I think this is due to the component beign a popup...
Thanks for the response :) 10 Apr 2007 07:15:24 -0700, Igor Costa <[EMAIL PROTECTED]>:
Hi there Carlos R. Did you used to popUp this new titlewindow using as IFlexDisplayObject data type? I'm not sure but this will works even if you have using it as on the fly for example import myComps.comCarlosTitleWin; var popMeUp:IFlexDisplayObject = mx.managers.popUpManager.createPopUp (comCarlosTitleWin,this); it will works smooth. Regards. On 10 Apr 2007 06:44:00 -0700, Carlos Rovira <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm facing a weird behaviour with creationPolicy in containers. I use > the default creationPolicy to auto and have a component with a TabNavigator > with this creation policy. If the instance of this component is created as > usual all works fine. The problem shows as I turn this component into a > TitleWindow and pops it with popup manager. In this new incarnation, the > component fires the creationComplete event in other tabs not selected (not > instantiated). > > This is a known effect of using a component in a popup manager?. I'm > making test and this problem only shows when change from default mxml > instantiation to a popup manager instantiation, so or this is a bug, or is > something expected. > > > > -- > ::| Carlos Rovira > ::| http://www.carlosrovira.com > ::| http://www.madeinflex.com > -- ---------------------------- Igor Costa www.igorcosta.org www.igorcosta.com skype: igorpcosta
-- ::| Carlos Rovira ::| http://www.carlosrovira.com ::| http://www.madeinflex.com
