flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mihai Chira (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLEX-35043) Unexpected behaviour of ListCollectionView.itemUpdated() when only one parameter supplied
Date Wed, 02 Mar 2016 08:44:18 GMT
Mihai Chira created FLEX-35043:
----------------------------------

             Summary: Unexpected behaviour of ListCollectionView.itemUpdated() when only one
parameter supplied
                 Key: FLEX-35043
                 URL: https://issues.apache.org/jira/browse/FLEX-35043
             Project: Apache Flex
          Issue Type: Bug
            Reporter: Mihai Chira
            Assignee: Mihai Chira


when calling itemUpdated(item) on a collection with only the first parameter provided (which
developers usually do to signal that some - unspecified - properties of the item have changed),
ListCollectionView.handlePropertyChangeEvents() would treat that as if the object has been
just introduced to the collection, replacing a null value - since oldValue was null, and property
was also null. (That's because the "property" value of the PropertyChangeEvent was null, which
was taken to mean that the oldValue - which was also null - was changed into that item, i.e.
the object reference changed in the collection, not just one of the object's properties.)
As such, it would try to remove that supposedly existing null value from the collection (and
sometimes a null does exist, but shouldn't be removed).



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

Mime
View raw message