Disabling is about interactivity, not creation, which is why creationComplete fires.
Somewhere you probably have code that sets enabled=true, and that code can call init(). Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of Scott Sent: Tuesday, September 01, 2009 11:01 AM To: [email protected] Subject: [flexcoders] creationcomplete firing when a component is disabled I've got a troubling issue... On my main page I have a tabNavigator that has several different pages for my app. This navigator is disabled until the user logs in. However, even though the navigator is disabled; it still fires off the creationcomplete which is giving me grief because the data connection hasn't been built yet. Falling short of creating a custom event, is there a way to fire off the init() function when the component is enabled instead of when it's creationComplete? Thanks Scott
