icollectionview

There are cases when you have many UI updates due a massive amount of INotifyChangedProperties events. In that case you might want to signal the changes to UI only once when all the properties are set like in a batch. I found this great article that explains how to defer the refresh of the ViewCollection: http://marlongrech.wordpress.com/2008/11/22/icollectionview-explained/ However I get an exception when the View is deferred and I try to add something to the collection. I don't understand why this shouldn't be allowed. That's the whole point of it in first place. InvalidoperationException:

I have a WPF ListView control, ItemsSource is set to an ICollectionView created this way: var collectionView = System.Windows.Data.CollectionViewSource.GetDefaultView(observableCollection); this.listView1.ItemsSource = collectionView; ...where observableCollection is an ObservableCollection of a complex type. The ListView is configured to display, for each item, just one string property on the complex type. The user can refresh the ListView, at which point my logic stores the "key string" for the currently selected item, re-populates the underlying observableCollection. The previous sort and

ObservableCollection s raise notifications for each action performed on them. Firstly they dont have bulk add or remove calls, secondly they are not thread safe. Doesn't this make them slower? Cant we have a faster alternative? Some say ICollectionView wrapped around an ObservableCollection is fast? How true is this claim. ObservableCollection can be fast, if it wants to. :-) The code below is a very good example of a thread safe, faster observable collection and you can extend it further to your wish. using System.Collections.Specialized; public class FastObservableCollection<T> :