When a single property changes, the list is marked dirty and all visible items will be redrawn on the next frame. Seems like we should be smarter about this, but we do it this way because we don't want to assume a property only affects one item. It could affect some other item via labelFunction or some other code.
Anyway, any other updates before the next frame essentially have no cost, so the only real factor is how much is visible. You can probably subclass DG, catch collection events and block them if you want to optimize further. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Stanislaw Fiedor Sent: Saturday, March 17, 2007 2:42 AM To: [email protected] Subject: [flexcoders] Some optimalization questions Hi! I've got some optimalization questions. What happens when a single property of the dataprovider of a List changes? Is the whole List and all its rows being redrawn or does it happen only to the row corresponding to the dataprovider item? What is the best 'CPUfriendly' practice when I have to update my List dataprovider quite often and it has got many items? stf
