[svn] 4607: Change the way we handle setItemAt in DataGroup.. we now do it synchronously again.

Question

Revision: 4607
Author: [email protected]
Date: 2009-01-21 10:45:20 -0800 (Wed, 21 Jan 2009)
Log Message:
Change the way we handle setItemAt in DataGroup..we now do it synchronously again. However, this has the consequence that, even temporarily, you are not allowed to have the save visual element listed twice in the data collection.
Get parity with Halo behavior and Flash behavior by allowing addElement()/addElementAt() to be called on an element already in the list. When this happens just shift the indices around.
Small ASDoc fix in GroupBase. Also, change the way we handle data being set int he default complex item renderer...this way we're not using binding, and the code is also easier to understand.
QE Notes: Write tests for addElement/addElementAt on items already in the group.
Doc Notes: None
Bugs: SDK-17909, SDK-18189
Reviewer: Hans
tests: checkintests, mustella DataGroup, List, Group, FxContainer, FxDataContainer
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17909
http://bugs.adobe.com/jira/browse/SDK-18189
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/DataGroup.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/Group.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/baseClasses/GroupBase.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/skins/spark/FxDefaultComplexItemRenderer. mxml
flex/sdk/trunk/frameworks/projects/wireframe/src/wireframe/FxDefaultComplexItemRenderer.m xml

Answer 1

Hi blabla12345,
(untested and without warranty)
replace this line:
const sSaveCUBE = "CUBE";
with this:
const sSaveCUBE = "cube";
Have fun