Binding to DataSeries.SelectedDataPoint

I am using a Chart control to display a series of points as a scatter plot. When a data point is selected, I'd like a details view to be populated with detailed information about the point that was selected. Ideally, I'd like to bind the details panel as such:

<ms:Chart>

<ms:ScatterSeries Name="ChartSeries">...</ms:ScatterSeries>

</ms:Chart>

<StackPanel Name="PointDetailsPanel" DataContext="{Binding ElementName=ChartSeries, Path=SelectedDataPoint.DataContext}" >

...

</StackPanel>

However, this does not work because it seems that ScatterSeries (or its parent DataSeries) does not implement INotifyPropertyChanged. Therefore, I'm forced to handle the MouseLeftButtonDown event and manually wire up the details panel DataContext in the code behind. This is a less than ideal situation. Are there any plans to make this and/or other control properties available to the WPF data binding system and have them work as expected? Or am I completely missing something?

Rather than implementing INotifyPropertyChanged, SelectedDataPoint will now be a dependency property instead.

 - Jason

A dependency property should work just fine. Great customer service, thanks!

I tried out the new DependencyProperty version of SelectedDataPoint. It *almost* works, but there's one more problem. My ScatterSeries ItemsSource is also bound to a source list. When the DataContext of the Chart changes, the ScatterSeries is redrawn to show the new data, but the SelectedDataPoint is still set to the previous data point which has been unloaded from the visual tree. I think the SelectedDataPoint should automatically be set to null in this case.

Again, I came up with a code-behind workaround, to manually set the previous point's IsSelected to false, like so:

private void TheChart_DataContextChanged(object sender, DependencyPropertyChangedEventArgs e) {

            if (ChartSeries.SelectedDataPoint != null) {

                ChartSeries.SelectedDataPoint.IsSelected = false;

            }

        }

Hello and thanks for pointing this out.

I have updated the logic to set the SelectedDataPoint property to null when appropriate. This fix will be available through the nightly builds from tomorrow the 29th of April. This will allow you to conveniently remove your local workaround.

 - Jason