Question

I hope someone can help me…

Josh Smith did a great article on “WPF apps with the Model-View View-Model”, and included in his article was the following code sample.

If you download the code sample and run the app and view all customers, then select a company (e.g. 4th company), then click “Create new customer” (which will open a tab of the new customer), and then click back on the “All Customers” tab, and then using the keyboard try and move the selected item up one to the item directly over the current selected item, it doesn’t! Instead the selector starts at the top again.

I am not sure why this happens, but I want it so that when you click up, it goes one item up, rather than starting at the top of the list. I suspect this has to do with FocusManager, but am not sure.

Does anyone know why the control behaves in this manner? Is it possible, and what approach I should take to modify this code and get it to not “reset” the selected item?

I have implemented a project based off this template and for functionality reasons I need to get the keyboard to move the selector up & down without it resetting.

Answer 1

in the example you’ve provided setting IsSelected property does not affect the logical focus so the focus is set by default. Workaround I have in mind currently is to force focus for the element in codebehind. As an example add handler to selectionchanged of the listview like this:

  private void ListView_SelectionChanged(object sender, SelectionChangedEventArgs e)
  {
    if (e.AddedItems.Count == 0 || e.RemovedItems.Count > 0) return;
    var item = (CustomerViewModel) e.AddedItems[0];
    var container = (UIElement) listView1.ItemContainerGenerator.ContainerFromItem(item);
    container.Focus();
  }