WPF Single Selection Across Multiple ItemsControls

Posted by gregsdennis on Stack Overflow See other posts from Stack Overflow or by gregsdennis
Published on 2012-09-21T03:24:59Z Indexed on 2012/09/21 3:37 UTC
Read the original article Hit count: 183

Filed under:
|
|

Part of my app has a month-view calendar interface, but I'm having trouble with item selection. The interface is set up so that each of the days in the view contains a ListBox of items, much like the month view in Outlook. The problem I'm experiencing is that I need to maintain a single item selection across all of the ListBoxes.

Below is a sample window that should adequately describe my situation. I need to maintain a single selection between both ListBoxes.

<Window x:Class="StackOverflow.MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        Title="MainWindow" Height="350" Width="525">
    <Grid>
        <Grid.ColumnDefinitions>
            <ColumnDefinition />
            <ColumnDefinition />
        </Grid.ColumnDefinitions>
        <ListBox ItemsSource="{Binding Numbers}"
                 SelectedItem="{Binding SelectedObject"/>
        <ListBox Grid.Column="1" ItemsSource="{Binding Dates}"
                 SelectedItem="{Binding SelectedObject"/>
    </Grid>
</Window>

In this primitive example, I would expect that when the SelectedObject property of my view model gets set to an item that's not in one ListBox, the selection would be removed in that ListBox, but that doesn't happen. I understand that I can simply name each ListBox, and hook into the SelectionChanged event. I'd prefer to not have to do that with an entire month-view calendar. There has to be a better way.

In a previous iteration of the app, I was able to create a SelectionManager static class with an attached property that was used to maintain selection. However, I can't use this now as the classes I'm using for my items are not DependencyObjects, and I'd really prefer not to have to create DependencyObject wrapper classes as this will considerably complicate my architecture.

Thanks.

© Stack Overflow or respective owner

Related posts about wpf

Related posts about selection