flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cosma Colanicchia (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-33774) grid.anchorRowIndex is reset to 0 when selection is programatically set (breaking further selection extend operations, e.g. SHIFT+CLICK)
Date Mon, 23 Sep 2013 14:42:07 GMT

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

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

    Attachment: TestGrid-screenshot.png

Attached screenshot of the test app, in the wrong state.
                
> 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: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message