Currently TabStripPlacement property is not stored on a RadPaneGroup as part of the xml when calling SaveLayout. The result is when this has been set to say "top", loading the same layout then causes all docked panes in the group to switch tab placement to the default of bottom - which is not the same as it was.
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.
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.
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.
Moving a ToolWindow when the DPI of the Window 7, 8 is higher then 100% causes incorrect offset to the mouse pointer to by applied. This issue leads to the following unexpected behaviors when ran under Window 8 OS: When the: - DragDropMode is set to Deferred. The compasses are not hidden after reorder. - AllowDragReorder is set to True. In this scenario you should be able to reorder tabs without the need to float team. The incorrect offset causes them to be floated making it impossible to reorder tabs as expected.
Available in LIB version 2016.3.1003, it will be also available in the R3 2016 SP1 Release.
If the mouse is above an AutoHideArea while the theme of the control is changing an NullReferenceException is thrown.
The same issue is observed when a WindowsFormsHost is placed inside RadPane. In that scenario the "made floating" animation of the RadPane instances is suppressed by the WindowsForms integration leading to flickering issues.
If the Background property of a RadPaneGroup is set in Windows8 and Office2013 themes it is disregarded
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
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.
It happens when the Pane is dragged and dropped not on the Compass several times, quickly.
Removing item from the PanesSource collection causes NullReferenceException
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.
When Saving and Loading a layout which has empty DocumentHost an ArgumentOutOfRangeException is thrown
Showing a ContextMenu inside the AutoHideArea causes it to be closed immediately. If a TextBox inside the AutoHideArea is right clicked the AutoHideArea is closed.
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.
Open a Window from a button placed inside the unpinned pane. The pane does not hide and the window is shown below it.