We could add support for different instances being hosted in separate Window elements that will support dragging and dropping operations.
Removing item from the PanesSource collection causes NullReferenceException
When Saving and Loading a layout which has empty DocumentHost an ArgumentOutOfRangeException is thrown
The fix will be available in the R1 2018 SP2 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.
When the content of a RadPane contains an ScrollViewer it is scrolled to its end when the RadDocking control is used in nested docking scenarios. Available with the 2015 Q3 release.
When used in second Tab in TabControl for example. Available with the R3 2016 SP1 release.
When move the most left pane in a split container above some other pane in the same split container the second splitter is created. Available in LIB version 2016.3.1017, it will be also available in the 2016 R3 SP1 release.
This only happens whenever the Panes are docked one above another in the DocumentHost.
Dynamically adding RadPane to PaneGroup, the header of the pane does not appear on the second added pane.
To workaround this the OnApplyTemplate() method can be called after the RadPane is added to the RadPaneGroup.
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.
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.
Hello Support,
we are using the RadDocking.LayoutChangeEnded event to store the docking layout (via RadDocking.SaveLayout) after the user has changed it.
When animations are enabled (default) everything works as expected and all groups, split containers, and panes are included when in the XML written by RadDocking.SaveLayout.
However, when disabling animations (either using AnimationManager.IsGlobalAnimationEnabled or custom styles for RadWindow and/or ToolWindow setting AnimationManager.IsAnimationEnabled to false) the RadDocking.LayoutChangeEnded event is raised too early.
The faulty behavior can be reproduced with the attached demo application as follows:
1. start the application (App.xaml includes a style for ToolWindow with animations disabled)
2. drag the pane "Solution Explorer" out of the application to create a new tool window
3. drag the "Solution Explorer" tool window onto the "Properties" pane's compass and drop it below "Properties", so that "Properties" and "Solution Explorer" are both pinned right in the application above each other
4. when inspecting the layout written to the "Output" pane you will find that the entry for the RadPane "Solution Explorer" is missing
Any additional change to the docking layout (like resizing a pane) will update the layout and show all panes again.
When enabling animations in the ToolWindow style the above steps will result in the complete layout being written to the "Output" pane.
Please let me know should you require further information for reproduction of this bug.
Best regards,
Oliver
If the mouse is above an AutoHideArea while the theme of the control is changing an NullReferenceException is thrown.
If the Background property of a RadPaneGroup is set in Windows8 and Office2013 themes it is disregarded