I have to grids each bound to ObservableCollections of the same data type.
If I programmatically remove an item from one collection and add it to the other collection, I get the following behavior:
1. The grid bound to the collection that the item is being removed from correctly updates.
2. The grid bound to the collection that the item is added to clears out all data, displaying only field labels. If I set the DataSource to null and then back to the collection, the grid redisplays correctly, showing the newly added data.
I'm building an interactive tool, and the top grid had grouping. An ideal user experience would leave group expansions in place (as the user had them) and simply add the new data to the correct group, or create a new group if need be (as is the case in my test).
Is there are better way to accomplish this, other than completely recreating the list each time an item is added, which is not good, at all.
Thank you.
Yes, I have two levels of grouping. In a perfect world, an item added to a collection would "magically" appear in the correct location of the grid. I might end up having to enumerate the groups before adding the item, saving off the "expanded" states so that I can restore them after reloading the grid to at least approximate the desired effect.
Is this issue fixed with 7.2? I'm still seeing the problem when its grouped and bound to an observable collection that changes.