The RadOutlookBar control takes a significant amount of time to load initially when it does not have a fixed width and its IsMinimized property is explicitly set to True.

A possible workaround, for the time being, is to set a fixed Width for the control and change its value in the Minimized and Restored events.

When you handle the selection change by displaying a dialog window and bring the mouse back to the current RadPaneGroup, the newly-selected pane becomes floating.

Resizing a dynamically added group results in a change of other groups' sizes, if the original groups were previously resized as well.

Currently, the length between the pane groups and split containers is hardcoded. Add a property on the docking, the pane groups or the containers that will allow to determine the length of the resizer (the RadGridResizer).

We could improve the drag-drop functionality of the RadDocking control when the FlowDirection="RightToLeft".

The CaptionHeight property of ToolWindow determines the height of the area where you can start dragging the window, starting from the top edge of the window. Currently, ToolWindow is using a fixed height based on the default title's content. However, the Title and TitleTemplate properties allow you to introduce a title with bigger height. In this case, if the title height is bigger than the default CaptionHeight, you cannot start dragging if the mouse is under the CaptionHeight's position.

Adjust the CaptionHeight dynamically, according to the actual title content height.

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

Currently, you can drag and drop panes only in their parent RadDocking control. Allow dragging from one RadDocking to another.

Currently, the RadPaneGroup has one Grid layout with Margin="5" present in its control template, which causes the Content of each child pane to be indented according to the Margin property's value.

To work this around, extract the control template, with x:Key="RadPaneGroupDocumentHostControlTemplate", and modify the Grid layout, which has its Margin property set to 5. After that, create a new style with TargetType="RadPaneGroup" and set its DocumentHostTemplate property, to the modified one.

When several unpinned panes are saved, each one of them is duplicated inside the generated XML. 

Add a visual element to display the exact drop location of an item, when reordering panes in a pane group.

Wrong order of the elements in the xml produced when saving the layout.

Allow floating panes from the auto-hide area as this can be done from a pinned RadPaneGroup.

Office2019 theme does not remove the ScrollViewerElement element when CanUserClose is set to False and the Visibility is set to Collapsed on a DocumentPane.

Hello Support,

 

I have some hidden panes (see attachement). The Problem is that when I try to reorder and save the layout and reload it, the panes are not ordered as wished.

 

I there a way to provide it?

 

Best regards,

Frédéric Le Blay.

The dropdown menu in the DocumentHost throws a NullReferenceException in newer themes when it is opened.

Instances of the NavigatorItemViewModel class stay in memory when using the DockingNavigator.

If the IsHidden property of a pane is set before the LoadLayout method is called and it also sets the IsHidden property of the pane, it is left in an invalid state  - with wrong visibility.

The visual clue, which shows where a ToolWindow will be dropped within the RadPaneGroup is not shown.

An unpinned RadPane that is being resized starts shrinking after it passes a certain threshold.