IMO, you want to set contentHeight as soon as you know what it will be. Every time it changes it can cause invalidations, although some of them are just to update the scrollbars.
If you look at RichEditableText, I think it actually computes the text size in the measure phase. -Alex On 10/5/14, 10:18 AM, "codekarma" <[email protected]> wrote: >Hi All, > >I have custom container that has Scroller as a child. TheScroller has an >another custom component as a viewport which implements IViewport (its >not a >Group). > >I'm trying to figure out at what point in the life cycle I need to >calculate >contentHeight & contentWidth in order to prevent unnecessary >invalidations. > >Currently I'm calculating it in the viewport's setActualSize method. The >viewport's contentHeight is set to a custom value but the contentWidth is >equal to explicit or measured width, it doesn't really need to be >calculated. This is the reason I am doing it in setActualSize. > >I think doing it in setActualSize causes multiple invalidation cycles >because setting the contentWidth/Height will trigger the scroller to >invalidate the display list. > >If anyone knows more on this or have suggestions please let me know. > >Thanks, >Purush > > > >-- >View this message in context: >http://apache-flex-users.2333346.n4.nabble.com/Implementing-IViewport-and- >setting-content-width-height-tp8297.html >Sent from the Apache Flex Users mailing list archive at Nabble.com.
