The Docking control must be placed inside DataTemplate.

Also it is possible to reproduce this behavior by executing this process:
  - Load a previously saved layout into the RadDocking control (note that the PanesSource is not set)
  - Set a PanesSource collection. Here the PanesSource objects are correctly added to the control but the previous items from the loaded Layout are not removed.

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

Changing the pane's state using context menu from floating to tabbed items leads to memory leak in MVVM scenario.

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

 With code below the radPane will remain hidden (radPane is floating pane):radPane.IsHidden = true; radPane.IsHidden = false;

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

With code below the radPane will remain hidden (radPane is floating pane):radPane.IsHidden = true;

radPane.IsHidden = false;

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

With code below the radPane will remain hidden (radPane is floating pane):radPane.IsHidden = true;

radPane.IsHidden = false;

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

If a SplitContainer's InitialPosition is set to FloatingDockable and the the layout is saved in the Unloaded event of the control, that SplitContainer is not shown after layout load.

The same could be observed if you float a Pane by dragging it out of its docked state.

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.

When DragDropMode is set to Deferred and Pane are moved around in the Docking control if the layout is saved and loaded some Panes are rendered incorrectly.

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

As a user of the control I want to be able to write custom logic for saving and loading the layout of the Docking control so that

- I can customize which elements should be saved (I want to exclude elements)
- I can describe how the elements should be loaded
- I can choose how the layout file is formatted
- I can choose which properties of a RadSplitContainer, RadPaneGroup or RadPane are saved

Available in the 2016 R2 release.

It would be useful to be able to customize the properties of the auto generated RadSplitContainer, RadPaneGroup and ToolWindow instances (created by floating, docking, pinning and unpinning of RadPane instances) based on the old RadPane instance.

For example the GeneratedItemsFactory methods could provide information about the RadPane for which SplitContainer etc is created.

Available in the 2016 R2 release.

When you create a custom PaneGroup by adding a class that inherits RadPaneGroup make it possible that the built-in Save/Load layout functionality loads those PaneGroups.

Available in the 2016 R2 release.

When Panes are placed above each other, after resizing their horizontal size, saving and loading the layout caused incorrect layout.

In some scenarios the SplitterChange is not rounded number and this cause invalid layout load. 

Workaround: Edit the saved xml and round the value.

When a Pane is floated and added to a specific position in a PaneGroup saving the layout saves its position as last Pane in the group

Available in LIB version 2016.1.411, it will be also available in the 2016 R2 release.

In nested RadDocking scenarios if the inner RadPane's content contains a ScrollViewer pressing "Tab" or "Tab + Shift" (keyboard navigation) the focus is moved out of the RadPane's content into the parts of the RadDocking.