Hi all, it's been a while since I posted on here but hopefully these suggestions will help someone else. They are not any major issues, just trying to make the controls easier to bind against.
I was wondering if it'd be possible to expose the set accessor for the SortDescriptors property on the RadGridView control. I was tasked recently with connecting the sorting of the control to requery the data from the RIA data source (which I got working) and this was one of the parts that could have been a bit easier to work with.
((ViewModelLocator)this.Resources["vml"]).MyViewModel.SortFields = radGridView1.SortDescriptors;
Granted all that was need was writing that single line of code in the code behind for the xaml page, but that wouldn't be necessary if the set accessor was available.
Also, the same thing could be said for the FilterDescriptors property on the RadDataFilter control. I had to connect this control to use RIA to change the where clause on the query that was filling the RadGridView. Without the set accessor being exposed, trying to bind to the collection INotifyPropertyChanged event from the base ObservableCollection from the CompoositeFilterDescriptorsCollection will cause you to miss the outermost and/or operator that's on the collection. So it was a requirement to use the same instance of the collection that the control was using.
((ViewModelLocator)this.Resources["vml"]).MyViewModel.Filters = dataFilter.FilterDescriptors;
Placing that line of code in the code behind fixes the issue, but it shouldn't need to be there. The view models need access to the same collection the controls use to ensure the interface gets updated if any are programmatically added or removed.
Just a couple suggestions I had working with the controls recently. Other than these couple relatively minor issues everything worked perfectly!
- Jeff