The the keyboard focus is also lost if you undock a RadPane from its docked state.
As a workaround you can persist the focus as shown in the RestoreFocusOnStateChanged SDK example, that can be found here:
https://github.com/telerik/xaml-sdk/tree/master/Docking/RestoreFocusOnStateChanged

Provide an easy functionality to exclude a pane or group of panes from reordering when AllowDragReorder is set to True.

If an custom implementation is implemented that restores the IsActive property state if a RadPane during the control's LoadLayout functionality the "Active" visual state if that RadPane instance is not cleared if different RadPane is selected.

This issue could be observed in the VisualStudioDocking located in the XAML GitHub repository here: https://github.com/telerik/xaml-sdk/tree/master/Docking/VisualStudioDocking

While the control's DragDropMode is set to Deferred and the RadPane instances contain content which is UI heavy, dragging those RadPane instances in order to reorder or re-dock them may experience performance issues leading to sluggishness of the drag and drop action.

When loading a previously saved layout that includes a floated RadPane located on a currently not available monitor, that RadPane should be made visible on the available monitor.

Currently its is directly loaded in its saved location which is not visible.

When the control contains RadPane instances which Content is provided by a MAF framework that content experiences flickers and disappearing when the RadPane is being floated, docked, pinned or unpinned.

By design in the current version of RadDocking when a hidden RadPane instance in a RadPaneGroup is made visible by changing the IsHiddden property of that pane to False, that RadPane is set to be SelectedItem in the group.


Make it possible to disable this functionality. This way the old selected RadPane in that RadPaneGroup will be persisted.

Pinning a pane instance will cause that instance's tab to go to the first place of the group in which it is in the DocumetnHost of the control. This behavior could be observed in MS Visual Studio 2013

Currently when ScaleTransform is used ether on the RadDocking control or its container the compasses/drop cues which are shown when docking a RadPane instance have incorrect scaling and are placed incorrectly.

By design the control's scaling is determined by the scaling of the OS environment.

This happens in particular scenario after saving/loading the layout.

Provide a sorted collection of the RadPane instances which would be activated by the built-in ActivationManager. 
This would make it possible to get the order of the currently shown ToolWindow instances.

 As a user I would like RadPane to have tooltips for show options, pin and close.

Currently the arrow buttons appear only when the TabStripPlacement is set to top.

Setting TabStripPlacement should be possible not only for RadPaneGroups but for the entire RadDocking control. That TabStripPlacement value should be used as default value for all the auto generated RadPaneGroups.