Dear Support,
I'm trying to bind the OutlookBar-Groups-Collection to a Collection view. The Groups are shown, but selection of a group does not fire the "CurrentChanged"-Event of the CollectionView.Furthermore .MoveCurrentToLast does not select the last Item in your OutlookBar. It does not work in any direction. In order to be sure that everythin is correct, I additionally bound a ListBox to the SAME Collection and everything works fine here. I assume that your OutlookBar does not work with MVVM.
Please check the following XAML and give us a hint how to combine your Product and a CollectionView: OutlookEntries is the collectionView
<igOutlookBar:XamOutlookBar DataContext="{Binding OutlookEntries, Mode=TwoWay}" GroupsSource="{Binding}" DockPanel.Dock="Left" HorizontalAlignment="Left" Name="OutBar" Width="200" IsTabStop="False" MaxWidth="600" MinWidth="100" Theme="Generic"> <igOutlookBar:XamOutlookBar.Resources> <Style TargetType="{x:Type igOutlookBar:OutlookBarGroup}"> <Setter Property="Header" Value="{Binding Header}"/> <Setter Property="SmallImage" Value="{Binding SmallImage}"/> <Setter Property="LargeImage" Value="{Binding LargeImage}"/> </Style> </igOutlookBar:XamOutlookBar.Resources> </igOutlookBar:XamOutlookBar>
voks said:I'm trying to bind the OutlookBar-Groups-Collection to a Collection view. The Groups are shown, but selection of a group does not fire the "CurrentChanged"-Event of the CollectionView.Furthermore .MoveCurrentToLast does not select the last Item in your OutlookBar. It does not work in any direction. In order to be sure that everythin is correct, I additionally bound a ListBox to the SAME Collection and everything works fine here. I assume that your OutlookBar does not work with MVVM.
Essentially what you are looking for is IsSynchronizedWithCurrentItem support in XamOutlookBar like the WPF Selector class (from which ListBox derives) has. I don't agree with saying that not having it means the control does not support MVVM. I would recommend submitting a suggestion for building support for this into the control. For now it is feasible to write your own attached behavior that does this. I have attached an example of doing so.
Thank you very much for your sample.
Didn't expected that much code for this issue. But thank you for the workaround. I will write a "feature request", nethertheless.
By the way, while studiing several threads here I found out that there are severel questions regarding MVVM with your controls. And it seems that there is a demand for a couple of such "feature requests".
Are there any plans from Infragistics for something like a complete re-check/overhaul of the WPF-Suite in order to support MVVM without workarounds? Would make our live much easier and save a lot of time at our end. As per my point of view, most of all WPF-Users do or should work with MVVM instead of CodeBehind. Of course, there are some exceptional cases but 3rd-Party-Controls should be such a case in my point of view.