flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maurice Amsellem (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-33813) Datagrid goes blank when assigning new dataProvider.source and calling refresh
Date Fri, 11 Oct 2013 15:34:42 GMT

    [ https://issues.apache.org/jira/browse/FLEX-33813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792722#comment-13792722

Maurice Amsellem commented on FLEX-33813:

h3. Workaround:

OK, so the workaround is the following:

rows.source = ....

Also, the rows.refresh() is not needed, as the source has been changed.
This is only needed when source does not change, but sorting / filtering has been applied.

> Datagrid goes blank when assigning new dataProvider.source and calling refresh
> ------------------------------------------------------------------------------
>                 Key: FLEX-33813
>                 URL: https://issues.apache.org/jira/browse/FLEX-33813
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: DataGrid
>    Affects Versions: Apache Flex 4.10.0
>         Environment: OS X, Apache Flex 4.10.0
>            Reporter: Gareth Daniel Smith
>            Assignee: Maurice Amsellem
>              Labels: datagrid, spark
>         Attachments: DataGridRender.zip
> Given a spark DataGrid with an ArrayCollection dataProvider, the DataGrid can erroneously
go blank in the following situation:
> - the DataGrid has been scrolled down so it is not at the very top.
> - the .source property is changed on the dataProvider to be a new Array where the new
values in the Array are also different objects to the objects in the previous .source Array.
> - .refresh() is called on the DataGrid
> This is possibly the same bug as FLEX-33066.
> I will attach a minimal test case.

This message was sent by Atlassian JIRA

View raw message