The grand theory of invalidation states that if your size properties may have changed, you call invalidateSize() and not invalidateDisplayList() and that if your size did change the framework will call invalidateDisplayList for you. Then if your size didn't change you won't waste time in updateDisplayList. However, there are lots of cases (probably the majority) where, even if your size didn't change you want to redraw so you call both. And as Bjorn said, the opposite is definitely true, and thus they are separate.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Schultheiss Sent: Monday, April 02, 2007 4:09 PM To: [email protected] Subject: Re: [flexcoders] invalidateSize() in tandem with invalidateDisplayList() I dont see where you would call invalidateSize() on its own (without a preceeding invalidateDisplayList() ) to often, if at all. But you would definitely call invalidateDisplayList() on its own without measure() so it is necessary that these two are seperate. On 03/04/2007, at 1:26 AM, lostinrecursion wrote: st().
