Changes between Initial Version and Version 6 of Ticket #2241


Ignore:
Timestamp:
01/22/15 10:22:46 (6 years ago)
Author:
abeham
Comment:

Created new ticket.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2241

    • Property Owner set to abeham
    • Property Status changed from new to reviewing
    • Property Summary changed from ItemsRemoved event uses Items instead of OldItems to store removed items to ItemsRemoved event handling is incorrect in some places
  • Ticket #2241 – Description

    initial v6  
    1 For most of our observable collections one has to subscribe to 4 events (ItemsAdded, ItemsReplaced, ItemsRemoved, and CollectionReset) to get notified of any change to the collection. Because of the reuse and generic design of the common event argument type it seems as if it was possible to handle these with one event handler. Unfortunately, ItemsRemoved is the exception in that it uses the `Items` property and not the `OldItems` property of the event argument to store the removed items.
     1A couple of item collection event handlers were implemented incorrectly for ItemsRemoved events.
     2Unification in event handling would be possible if ItemsRemoved was using OldItems property to store removed items. This is described in ticket: #2297.
    23
    3 It should be evaluated if the design could be improved, e.g. these events could be unified to one event and thus requiring only one subscription if the Items and OldItems property would be used consistently.
     4Here the bugs should be fixed.