The AutoHide area is closing when clicking at WinForms control placed in it.
The issue also can be reproduced with WebBrowser or any object of MarshalByRefObject type placed in the AutoHideArea.

Available in LIB version 2016.3.1003, it will be also available in the R3 2016 SP1 Release.

AutoHideArea is opening when pin/unpin another Pane

Add overloads for LoadLayout and SaveLayout methods of the Docking control with parameter of type XElement instead of Stream. Change the Save/Load layout code to use LinqToXML instead of XmlReader and XmlWriter.

If there are more than 2 Panes in an PaneGroup closing one of the Panes with index bigger than 1 calls ActivePaneChanged  event twice.

Reorder a pane and save the layout. Reorder another pane and load the layout - the wrong pane is selected.

When using Implicit Styles setting the DropDownDisplayMode of a PaneGroup to Visible in the Office themes causes the DropDownButton to be invisible.

When the Dock's auto-hide area is is about to be shown on two monitors simultaneously it is shown only on one of the monitors.

The popup that becomes visible when hovering over a pinned pane is cut when ScaleTranform is set to the RadDocking control.

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

Workaround: Edit the saved xml and round the value.

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.

If you have RadPane inside DocumentHost and you try to set IsHidden=true after InitializeComponent, it will not be applied and the pane will remain visible.

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.

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

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

- Binding Ishidden property of each pane to a menu section
- Save/Load the Docking layout on closing and opening the application
- Adding documents to module section using MVVM (DocumentHost)
- Persiste the state of each RadPane's content using PersistenceFramework.

If you have more than one monitors and on one of them you maximize a ToolWindow, than dock another pane and undock it, the second pane's width will be equal to the width of the two monitors. 

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.

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.

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