1. Create an app using RadDocking. The 'First Look' demo of RadDock can be modified to reproduce the problem.
2. Modify one of the panes, replace the TextBlock control with a TextBox control. Bind the text of the TextBox control to a string property.
3. Add the string property to the .cs file and in the setter, Show a MessageBox.
4. Run app. Select tab with Textbox control and modify the value.
5. Now select the other tab. the messagebox will be displayed. Notice it can be dismissed via keyboard but not via mouse click. It cannot be moved via mouse either.
6. Select a window outside of the application and not select the message box. Notice Mouse input now works. MessageBox can be moved and dismissed via mouse.

ToolWindow does not respect the "Show window contents while dragging" setting when it is first floated.

If DragDropMode is set to Deferred when trying to dock a Pane inside a compass that is over the dragged Pane, the dock operation is not completed correctly.

Available in LIB version 2016.2.516, it will be also available in the R2 2016 SP1 Release.

Available in LIB version 2017.1.410 , it will be also available in the R2 2017 Release. 

The compass elements are not on the proper places when the docking is on the second monitor. To reproduce this the DPI of the monitors should be different for example 125% (main) and 150% (secondary). Also, to reproduce this you will need to enable the DPI awareness of the application by setting the dpiAware and dpiAwareness settings in the app.manifest file.

Steps to reproduce:
1. Start the WPF Controls Example application on a terminal server
2. Select Docking example
3. Try to move a floating windows by dragging it with the mouse
4. The window will move for a split second, but stop moving after that. (It behaves as if the mouse button was released after the initial move)

The compass is out of place when specific height is set to the dock and the window is made smaller than the docking height

In WPF when show the unpined pane by hovering, when right click to show the contextmenu the pane collapses.

Description:

When using a display with scaling setting to more than 100%, floating pane docking does not work as intended. When dragging a pane out of a PaneGroup, and without releasing it, you drop it on top of another tab (so it is inserted into that position in the PaneGroup), nothing happens (window stays floating in that position). If you drag the already floating window on top of the same tab, then the default behavior happens and the pane is docked into the group. This behavior is reproducible on the Telerik UI for WPF Demo app.

See attached video for reproduction case in Demo app.

 

Technical Details:

For the failing scenario DragDelta on the ToolWindow is being triggered with wrongly scaled mouse position. On second drag drop operation, DragDelta receives properly scaled mouse position.

Failure case mouse positions:

DRAG START {864,128.8}
DRAG DELTA {871.2,142.4}
...
DRAG DELTA {864.8,114.4}
DRAG END {1081,143}

Second case mouse positions:

DRAG START {862.4,116}
DRAG DELTA {873.6,160.8}
...
DRAG DELTA {860.8,112}
DRAG END {860.8,112}

If the IsHidden property of a Pane placed inside the Document host is bound to a property in the ViewModel with value of True the IsHidden property at start-up is reset to False.

The compass is misplaced on the second monitor when launching *.exe on monitors with higher DPI. The tool window also is not positioned correctly. 

  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitor</dpiAwareness>
      <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
    </windowsSettings>
  </application>

 

This leads to loading wrong Template whenever the layout is loaded.

A possible workaround has been demonstrated in the attached project.

When a pane is unpinned, mouse over it in order to show. After that when the mouse is removed from the pane it flickers before the animation is started.

Create content control and change the content in it -when the content contains RadDock the WPF window lose focus.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.