There is a problem described at this link:
http://www.telerik.com/help/silverlight/gridview-troubleshooting-first-row-always-selected.html
about the first row of a grid always being selected. This page states that the problem does not occur in version Q2 2010 or later. However, I have seen the same problem using Q2 2011 SP1, when using Visual Studio 2010 SP1. The problem does not occur when using Visual Studio 2010 without SP1.
The first row is not selected when the page is first displayed, but when I navigate away from the page and then back to it, then the first row of all of the grids on that page are selected, and the SelectionChanged event is being fired. The grids are within a navigation frame. We navigate between the frames using a selection from a combo box like this:
The workaround stated in the above referenced link (i.e. setting IsSynchronizedWithCurrentItem to false) fixed the problem for us. But, it doesn't seem like the problem is really resolved as stated in the link. Again, this only shows up when we use VS 2010 with SP1. We've built the exact same solution with SP1 and without SP1 and we don't see this behavior without SP1.
http://www.telerik.com/help/silverlight/gridview-troubleshooting-first-row-always-selected.html
about the first row of a grid always being selected. This page states that the problem does not occur in version Q2 2010 or later. However, I have seen the same problem using Q2 2011 SP1, when using Visual Studio 2010 SP1. The problem does not occur when using Visual Studio 2010 without SP1.
The first row is not selected when the page is first displayed, but when I navigate away from the page and then back to it, then the first row of all of the grids on that page are selected, and the SelectionChanged event is being fired. The grids are within a navigation frame. We navigate between the frames using a selection from a combo box like this:
private void RadComboBoxItem_Selected(object sender, RoutedEventArgs e)
{
this.navFrame.Navigate(new Uri(((Telerik.Windows.Controls.RadComboBoxItem)sender).Tag.ToString(), UriKind.Relative));
}
The workaround stated in the above referenced link (i.e. setting IsSynchronizedWithCurrentItem to false) fixed the problem for us. But, it doesn't seem like the problem is really resolved as stated in the link. Again, this only shows up when we use VS 2010 with SP1. We've built the exact same solution with SP1 and without SP1 and we don't see this behavior without SP1.