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.
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.
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.
Make it possible to dock panes inside and outside of the DocumetnHost via it's compasses
After certain expand/collapse of RadExpander that is placed inside a floating RadPane the DataContext of the RadExpander is lost
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.
The RestrictedAreaMargin should be used as a starting point for the position when a ToolWindow is being maximized.
Available in LIB version 2016.3.1003, it will be also available in the R3 2016 SP1 Release.
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.
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.
Currently Minimize\Restore\Maximize buttons are not shown in the ToolWindow's header, so there are some inconveniences in use. For example, it's impossible to minimize tool windows easily.
If the Background property of a RadPaneGroup is set in Windows8 and Office2013 themes it is disregarded
I have a scenario where I only want to unhide the pane when certain property of the document is true. For example: I have 3 panes A,B and C Panes A and C are visible. Active Pane should always be Pane A. By default pane (B) is hidden. Now when I set the IsHidden Property of the pane B to FALSE. Pane B now becomes the active pane. I still want Pane A to be the Active Pane, but show the Pane B in background. If I try setting the Pane A to be the active pane after Pane B is shown. It flickers which you can see here http://screencast.com/t/dGvU7UwUyYp Is there any way i can unhide the pane in background while the active pane remains the same without having this flickering scenario.
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
Exception is thrown when running RadDocking in separate thread.