Makes sense, but I tried that already...
<mx:Canvas xmlns:mx="http://www.adobe.com/2006/mxml"; width="100%" height="100%" enabled="false" creationComplete="init()" > Still causes the init() to fire... Is this a bug? sj ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Alex Harui Sent: Tuesday, September 01, 2009 1:49 PM To: [email protected] Subject: [flexcoders] RE: creationcomplete firing when a component is disabled 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 <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 -- This message has been scanned for viruses and dangerous content by MailScanner <http://www.mailscanner.info/> , and is believed to be clean.
