flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik de Bruin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLEX-34657) SelectedIndices order is messed up
Date Mon, 02 Feb 2015 09:25:35 GMT

     [ https://issues.apache.org/jira/browse/FLEX-34657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Erik de Bruin closed FLEX-34657.
--------------------------------
    Resolution: Fixed

The issue as reported has been solved, please look at the Mustella tests I created to compare
previous to current behavior - the commented asserts show the 'old/wrong' values.

> SelectedIndices order is messed up
> ----------------------------------
>
>                 Key: FLEX-34657
>                 URL: https://issues.apache.org/jira/browse/FLEX-34657
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: List
>    Affects Versions: Apache Flex 4.13.0
>            Reporter: Chris Velevitch
>            Assignee: Erik de Bruin
>             Fix For: Apache Flex 4.14.0
>
>         Attachments: Main.mxml
>
>
> The order of the existing selected indices is reversed each time a item is selected or
deselected.
> In spark.components.list.as, the function calculateSelectedIndices at line 1646, the
loop is using splice to rebuild the selected indices. This is reversing the order of the previously
selected indices before adding the new item. The loop should be using push to preserve the
original order.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message