[svn:fx-trunk] 4982: Moving DataGroup from item based lookup to an index based lookup.

Question

Revision: 4982
Author: [email protected]
Date: 2009-02-16 23:31:05 -0800 (Mon, 16 Feb 2009)
Log Message:
Moving DataGroup from item based lookup to an index based lookup. Also, we now cleanup old item renderers when the dataProvider changes. This solves some memory leak problems.
Because of this, we should now be able to deal with duplicate items again.
We still need to work on data collection changes in the virtual layout case.
QE Notes: Please add the tests for dup items back in
Doc Notes: -
Bugs: SDK-19245, SDK-18043
Reviewer: Hans
tests: checkintests, DataGroup and FxList mustella tests (some new ones failed, but are really due to SDK-19287, and these tests should be excluded to that bug now)
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19245
http://bugs.adobe.com/jira/browse/SDK-18043
http://bugs.adobe.com/jira/browse/SDK-19287
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/DataGroup.as

Answer 1

GREAT info, but it may be helpful to note that when replacing a portion of the variable "Countries" with a whitespace character, you may cause the workflow to fail in a few specific cases (certain lookup fields will not accept this and will automatically
cancel).  I only found this out when recreating your workflow on a similar, but much more complex list set.  
To resolve this issue, I used another utility action (Extract Substring from Index of List) to clear out the whitespace.  I configured it as "Copy from
Variable: Countries, starting at
1 (Output to Variable: Countries), which takes care of this issue in those few cases.
Otherwise, WOW!  AWESOME JOB!  Thanks!  :)