[
https://issues.apache.org/jira/browse/FLEX-34140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933112#comment-13933112
]
Maurice Amsellem commented on FLEX-34140:
-----------------------------------------
AFAIU, these events (ADD / REMOVE / REPLACE / RESET / REFRESH) are mainly used
to incrementally update dependents of the modified collection (instead of
recomputing everything).
old values are there to help computing the updates.
I don't see what the "revertable" means and how you use it? it this to revert
user actions ? undo action or something?
Can you please clarify the use case.
> Add oldValue property to Collection event(
> CollectionEventKind.REFRESH/CollectionEventKind.RESET )
> --------------------------------------------------------------------------------------------------
>
> Key: FLEX-34140
> URL: https://issues.apache.org/jira/browse/FLEX-34140
> Project: Apache Flex
> Issue Type: Task
> Components: Collections
> Reporter: Gary Yang
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> For a CollectionEvent, when event kind is
> CollectionEventKind.Add REPLACE REMOVE MOVE UPDATE
> it is revertable, because for ADD/REMOVE, developers can call REMOVE/ADD, for
> MOVE, there's a oldLocation; for REPLACE: the items are PropertyChangeEvent
> which has oldValue.
> but for CollectionEventKind.REFRESH and RESET, it is NOT revertable!!!
> If Flex can add a new oldValue or oldList, ( or depreciated: give developers
> a event right before dispatching ), Flex will be better!!!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
