exactly what you don't need actually. :) Although that may work for you,
its not a good practice as this turns off the deferred instantiation
inherent to TabNavigator among others components. This means that all your
tabs are created immediately regardless if they are ever viewed, slowing
startup times. Better to use other event such as creationComplete, etc.
DK
Douglas Knudsen
http://www.cubicleman.comthis is my signature, like it?
On Mon, Aug 24, 2009 at 1:30 PM, Willy Ray <
willyray@...> wrote:
>
> Oh Yes! That's EXACTLY what I needed! Thank you!
>
> /w
>
> On Mon, Aug 24, 2009 at 11:26 AM, <
brad@...> wrote:
> >
> > If I'm following you, I think you need to look into the creationPolity
> > property.
> >
> >
>
http://livedocs.adobe.com/flex/3/html/help.html?content=layoutperformance_05.html> >
> > ~Brad
> >
> > -------- Original Message --------
> > Subject: Components in tabNavigator not initialized
> > From: Willy Ray <
willyray@...>
> > Date: Mon, August 24, 2009 11:58 am
> > To: flex <
flex@...>
> >
> >
> > Hey guys,
> >
> > Here's the issue:
> >
> > I have a tabNavigator that basically looks like this:
> >
> > My problem is that I need all the components in all the tabs to be not
> > null from the very beginning. I need, for example, to be able to set
> > details.addEventListener() in the creationComplete function of the
> > application... but details is NULL until it's been clicked on.
> >
> > One way might be to refactor the creation of everything here into
> > actionscript, but it would be a long and tedious refactoring, and I
> > don't have the time. Thoughts?
> >
> >
> >
> >
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists
Archive:
http://www.houseoffusion.com/groups/flex/message.cfm/messageid:6053Subscription:
http://www.houseoffusion.com/groups/flex/subscribe.cfmUnsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=17837.14401.37