You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/09/22 22:36:34 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14143765#comment-14143765 ]
ASF GitHub Bot commented on FLEX-33774:
---------------------------------------
Github user bigosmallm commented on the pull request:
https://github.com/apache/flex-sdk/pull/7#issuecomment-56438849
Looks like this fixes FLEX-33774. Would be nice if someone gave it a shot.
> 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-screenshot.png, TestGrid.mxml, TestGrid.mxml
>
>
> 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.3.4#6332)