Free cookie consent management tool by TermsFeed Policy Generator

Changes between Initial Version and Version 1 of Ticket #1971, comment 7


Ignore:
Timestamp:
07/24/13 10:46:02 (11 years ago)
Author:
gkronber
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1971, comment 7

    initial v1  
    11Replying to [comment:6 gkronber]:
    22> I found that similar code also exists for instance in ItemListView. Is it useful to make the same change in all views that support AddRange/RemoveRange?
    3 Yes, the ItemsListView should also be adapted. However, I found another issued, which I don't know how to resolve correctly. If a collection contains duplicate items, currently the first reference to it is removed, regardless of the selection. So the question is how to deal with duplicates in collections (not only regarding deletion)?
     3Yes, the ItemsListView should also be adapted. However, I found another issue, which I don't know how to resolve correctly. If a collection contains duplicate items, currently the first reference to it is removed, regardless of the selection. So the question is how to deal with duplicates in collections (not only regarding deletion)?
    44
    55The deletion is handled in a better way in ListViews, because there the items are removed according to their index and so duplicates are no issue.