[flexcoders] updateDisplayList() called before commitProperties()

2012-09-26 Thread Dave Glasser
I have a custom component and the first time updateDisplayList() is called, it 
is called before commitProperties() has been called for the first time. It 
still happens even after I put:

invalidateProperties();

in the constructor.

The stacktrace looks like this:

    at mx.core::UIComponent/validateDisplayList()
    at com.package.MyClass/validateDisplayList()
    at mx.managers::LayoutManager/validateDisplayList()
    at mx.managers::LayoutManager/doPhasedInstantiation()
    at Function/http://adobe.com/AS3/2006/builtin::apply()
    at mx.core::UIComponent/callLaterDispatcher2()
    at mx.core::UIComponent/callLaterDispatcher()

I'm using Flex 4.6. Is this proper behavior?


Re: [flexcoders] updateDisplayList() called before commitProperties()

2012-09-26 Thread Alex Harui
If you are adding the component in the updateDisplayList of a parent, I think 
that can happen.  The List classes call validateClient on components added in 
updateDisplayList in order to get them through their other phases.


On 9/26/12 12:35 PM, Dave Glasser dglas...@pobox.com wrote:






I have a custom component and the first time updateDisplayList() is called, it 
is called before commitProperties() has been called for the first time. It 
still happens even after I put:

invalidateProperties();

in the constructor.

The stacktrace looks like this:

at mx.core::UIComponent/validateDisplayList()
at com.package.MyClass/validateDisplayList()
at mx.managers::LayoutManager/validateDisplayList()
at mx.managers::LayoutManager/doPhasedInstantiation()
at Function/http://adobe.com/AS3/2006/builtin::apply()
at mx.core::UIComponent/callLaterDispatcher2()
at mx.core::UIComponent/callLaterDispatcher()

I'm using Flex 4.6. Is this proper behavior?





--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Re: [flexcoders] updateDisplayList() called before commitProperties()

2012-09-26 Thread Dave Glasser
That's what it was.

Many thanks!





 From: Alex Harui aha...@adobe.com
To: flexcoders@yahoogroups.com flexcoders@yahoogroups.com 
Sent: Wednesday, September 26, 2012 3:53 PM
Subject: Re: [flexcoders] updateDisplayList() called before commitProperties()
 

 Re: [flexcoders] updateDisplayList() called before commitProperties() 


If you are adding the component in the updateDisplayList of a parent, I think 
that can happen.  The List classes call validateClient on components added in 
updateDisplayList in order to get them through their other phases.


On 9/26/12 12:35 PM, Dave Glasser dglas...@pobox.com wrote:



 
 
   

I have a custom component and the first time updateDisplayList() is called, it 
is called before commitProperties() has been called for the first time. It 
still happens even after I put:

invalidateProperties();

in the constructor.

The stacktrace looks like this:

at mx.core::UIComponent/validateDisplayList()
at com.package.MyClass/validateDisplayList()
at mx.managers::LayoutManager/validateDisplayList()
at mx.managers::LayoutManager/doPhasedInstantiation()
at Function/http://adobe.com/AS3/2006/builtin::apply()
at mx.core::UIComponent/callLaterDispatcher2()
at mx.core::UIComponent/callLaterDispatcher()

I'm using Flex 4.6. Is this proper behavior?

   



-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui