Input bindings

Hi Joe,

That is an interesting problem to try and solve.  The reason is as you said, the floating docking windows are contained in a separate WPF Window and keyboard shortcuts don't carry across to other Windows.  Floating tool windows are already set up to be "owned" by the main Window.

We have this method defined on DockSite:

protected virtual void InitializeFloatingWindow(Window window) {}

You are able to override that method and it will fire whenever a new Window is created to host floating docking windows.  Thus that would be a perfect place to attach to a key event or add commands.  I'm curious what you think is best for your scenario.

This is the code I added to that function:

protected virtual void InitializeFloatingWindow(Window window)
{
	// Copy owner window input bindings to the new window.
	Window ownerWindow = VisualTreeHelperExtended.GetAncestor<Window>(this);
	if (ownerWindow != null)
	{
		window.DataContext = ownerWindow.DataContext;
		window.InputBindings.AddRange(ownerWindow.InputBindings);
	}
}

This does work but I get a warning for every input bindind that gets copied over. These warnings only happen on initializing the first floating window. Here is what the warning looks like:

System.Windows.Data Error: 2 : Cannot find governing FrameworkElement or FrameworkContentElement for target element. BindingExpression:Path=Workspace.SaveAllCommand; DataItem='MainWindowVM' (HashCode=25056856); target element is 'KeyBinding' (HashCode=40484047); target property is 'Command' (type 'ICommand')

I tried delaying it a frame to see if WPF resolves what ever it needs to but I couldn't get the warnings to go away.

Joe

Hi Joe,

It's hard to say without seeing it.  Do you mind packaging up a minimal sample that shows it happening and send that over so we can have a look?  Please email it to our support address and reference this thread in your email.  Be sure to rename the .zip file extension so it doesn't get spam blocked.  Thanks!