Comments on: When it is time to reset dirty flag “invalidatePropertiesFlag” in Flex invalidation framework? http://www.jabbypanda.com/blog/2009/12/when-it-is-time-to-reset-dirty-flag-invalidatepropertiesflag-in-flex-invalidation-framework/ it's RIA, not Rio Fri, 20 Jan 2012 06:59:00 +0000 hourly 1 http://wordpress.org/?v=3.3 By: JabbyPanda http://www.jabbypanda.com/blog/2009/12/when-it-is-time-to-reset-dirty-flag-invalidatepropertiesflag-in-flex-invalidation-framework/comment-page-1/#comment-64918 JabbyPanda Thu, 20 Jan 2011 09:31:12 +0000 http://www.jabbypanda.com/blog/?p=54#comment-64918 The highly relevant discussion on this matter http://www.tikalk.com/flex/invalidate-calls-within-commitproperties The latest comment under this discussion is suggesting to do exactly the same with processing multiple invalidated properties during the single validation process what you've been already doing. The highly relevant discussion on this matter

http://www.tikalk.com/flex/invalidate-calls-within-commitproperties

The latest comment under this discussion is suggesting to do exactly the same with processing multiple invalidated properties during the single validation process what you’ve been already doing.

]]> By: Roman Protsiuk http://www.jabbypanda.com/blog/2009/12/when-it-is-time-to-reset-dirty-flag-invalidatepropertiesflag-in-flex-invalidation-framework/comment-page-1/#comment-64903 Roman Protsiuk Wed, 19 Jan 2011 16:44:15 +0000 http://www.jabbypanda.com/blog/?p=54#comment-64903 When it's possible I always try to process properties that can invalidate other properties first, and those others second. If it's impossible another approach would be invoking invalidateProperties via callLater. When it’s possible I always try to process properties that can invalidate other properties first, and those others second.
If it’s impossible another approach would be invoking invalidateProperties via callLater.

]]>