You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Cosma Colanicchia (JIRA)" <ji...@apache.org> on 2013/10/14 18:24:49 UTC

[jira] [Updated] (FLEX-33774) grid.anchorRowIndex is reset to 0 when selection is programatically set (breaking further selection extend operations, e.g. SHIFT+CLICK)

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

Cosma Colanicchia updated FLEX-33774:
-------------------------------------

    Attachment: Grid.patch
                TestGrid.mxml

Here is an update on the TestGrid app, along with a patch attempt (yet to be fully tested)

> grid.anchorRowIndex is reset to 0 when selection is programatically set (breaking further selection extend operations, e.g. SHIFT+CLICK)
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-33774
>                 URL: https://issues.apache.org/jira/browse/FLEX-33774
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: DataGrid
>         Environment: Windows 7 64bit
>            Reporter: Cosma Colanicchia
>         Attachments: Grid.patch, TestGrid.mxml, TestGrid.mxml, TestGrid-screenshot.png
>
>
> When the selectedItems are programatically set on a DataGrid instance, the internal grid.anchorRowIndex is incorrectly reset to 0, even if displayed selection feedback is correct. When extending selection with SHIFT+CLICK on other rows, this incorrect value is computed and the new selection always starts from the first row.



--
This message was sent by Atlassian JIRA
(v6.1#6144)