Hello,
I have a problem with auto hiding tool windows. The problem may or may not be caused by your docking code but as I have never come across a similar issue I tend to believe there is a connection.
Please consider two dockable/autohide tool windows. Both host the same ListBox. The only difference between them is the way ItemsSource is bound. Now imagine two TextBlocks in the workspace, each bound to SelectedItem of one of the ListBoxes. When run all works as expected. Changing the selection in each of the ListBoxes reflects in their corresponding TextBlocks. The problem arises when one unpins the tool windows. One of the ListBoxes loses the current selection while the other one maintains it even when hidden.
ItemsSource of the first ListBox is bound to a property using ElementName (this one works) and the other one is bound relying on DataContext which is set previously on a parent element (this one does not work).
Both ListBoxes are essentially bound to the same collection but because of the difference in data binding, they behave differently.
I am sending the sample project that reproduces the issue to your support mail.
Thanks for looking into this issue.
I have a problem with auto hiding tool windows. The problem may or may not be caused by your docking code but as I have never come across a similar issue I tend to believe there is a connection.
Please consider two dockable/autohide tool windows. Both host the same ListBox. The only difference between them is the way ItemsSource is bound. Now imagine two TextBlocks in the workspace, each bound to SelectedItem of one of the ListBoxes. When run all works as expected. Changing the selection in each of the ListBoxes reflects in their corresponding TextBlocks. The problem arises when one unpins the tool windows. One of the ListBoxes loses the current selection while the other one maintains it even when hidden.
ItemsSource of the first ListBox is bound to a property using ElementName (this one works) and the other one is bound relying on DataContext which is set previously on a parent element (this one does not work).
Both ListBoxes are essentially bound to the same collection but because of the difference in data binding, they behave differently.
I am sending the sample project that reproduces the issue to your support mail.
Thanks for looking into this issue.