Generally there should be one and only one correct path of validation of properties so you don't need to go back as that is going to cost you time. The pattern is usually to set a flag (myPropertyChanged) when the property is in need of validation, and you can check at the end of your commitProperties for these flags and simply call commitProperties recursively.
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 Manish Jethani Sent: Wednesday, May 27, 2009 12:14 PM To: [email protected] Subject: Re: [flexcoders] Re: Calling invalidateProperties during validateProperties On Wed, May 27, 2009 at 11:10 PM, reflexactions <[email protected]<mailto:reflexactions%40yahoo.com>> wrote: > Well an example would be where there say half a dozen related properties that > get set, these individualy call invalidateProperties and will then be > collectively processed in commitPorperties on the next frame. > > In that processing events are raised to notify changes, however the handlers > for those events could lead to other properties being set that in turn will > call invalidateProperties which of course fails. I don't know if dispatching events from commitProperties(), measure(), updateDisplayList(), etc., is supported. Maybe somebody from the Flex team can throw some light on this. I would use callLater() to dispatch that event. My $0.02. Manish
