Hello,
I've extended your grid in hopes of providing consistency for other developers. In order to enable paging, I created a class to wrap and hopefully hide the use of the virtual collection from the end user. I basically have them bind to a dependency property for their itemSource. Then in the extended class I take that and use it to populate the virtualcollection which is assigned to the itemsSource of the grid.
This works well as long as the grid is bound to one collection. In some cases we have a combobox that will change the datasource of the grid. When this happens the virtualcollection seems to get a little messed up. I've spent quite a lot of time trying to figure out what could be causing it and was hoping someone might be able to help me.
I have a sample application running that I can provide.
Thanks,
Scott
Hello Scott,
I am still following your case. I am just checking the progress of this ticket and if you need any more assistance.
Regards Petar.
I see what you mean and this doesn’t really sound like an isolated sample and we since we don’t really assess custom implementations I was wondering if you haven’t been able to reproduce it on simpler project. If you haven’t pinpoint the cause of the behavior I can suggest you explain what the issue is exactly and what modifications have you made to the XamGrid to reproduce it.
Looking forward to hearing from you.
Hello Petar,
I have a rather large zip file (28MB) that has an example demonstrating the issue I'm having. I can provide this to you if you wish.
I have read through your explanation and I would need some more details in order to start looking into the exact issue in particular. If you can give us an isolated sample that would be great.