On Wed, May 27, 2009 at 11:10 PM, reflexactions <[email protected]> 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
