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

Mihai Chira updated FLEX-34837:
-------------------------------
    Attachment: gridSortedByDateValueInsteadOfLabel.png

After these changes the sorting for Date values (as long as the column doesn't 
have a formatter) applies to the value of the date, not to the label. Is this 
desirable / acceptable? To me it makes more sense than to sort by the string 
displayed.

When there is a formatter, however, we cannot be sure that the user gets to see 
all the components of the Dates which mean that they're shown in the order of 
the value. For example, they may only be shown the month and year, but not the 
date of the month. So in that case we're ordering by the string displayed.

> DataGrid sorted with complex dataField doesn't keep track of changes to those 
> fields, leading to RTE when trying to remove selected item
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-34837
>                 URL: https://issues.apache.org/jira/browse/FLEX-34837
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: DataGrid
>    Affects Versions: Apache Flex 4.14.0
>            Reporter: Mihai Chira
>            Assignee: Mihai Chira
>             Fix For: Apache Flex 4.15.0
>
>         Attachments: FLEX-34837.ZIP, gridSortedByDateValueInsteadOfLabel.png
>
>
> *Steps to reproduce*: run attached application (steps are on the stage).
> *Note* that GridItemEditor.save() has a trick to re-run the sort, but a 
> custom grid editor or a programmatic change will not do that trick, leading 
> to the RTE.
> Another summary for this issue could be *ListCollectionView doesn't keep 
> track of changes to the complex fields it's being sorted by*.



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

Reply via email to