0 Replies Latest reply on Jan 21, 2009 10:45 AM by (Ryan_Frishberg)

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

    Level 1
      Revision: 4607
      Author: rfrishbe@adobe.com
      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:

      Modified Paths:
      flex/sdk/trunk/frameworks/projects/flex4/src/mx/skins/spark/FxDefaultComplexItemRenderer. mxml
      flex/sdk/trunk/frameworks/projects/wireframe/src/wireframe/FxDefaultComplexItemRenderer.m xml