Last Updated: 13 Nov 2020 18:09 by ADMIN
Release LIB 2020.3.16
When the CloseTabsOnMouseMiddleButtonDown property is set to True and the user clicks on an unselected tab, it will be not closed, the selected one is closed instead. 
Last Updated: 13 Oct 2020 14:49 by ADMIN
Release R3 2020 SP1
Setting CloseTabsOnMouseMiddleButtonDown on the RadPaneGroup to true will not respect CanUserClose property of RadPane set to false.
Last Updated: 06 Nov 2020 13:59 by ADMIN
Release LIB 2020.3.1109 (11/09/2020)
The ToolWindows of the RadDocking control remain open even if the application is minimized when a remote connection is restored.
Last Updated: 29 Oct 2020 08:02 by ADMIN
Release LIB 2020.3.1102 (11/02/2020)
When clicking a RadGridResizer element while a context menu is open, the RadSplitContainer is resized. 
Last Updated: 24 Aug 2020 10:56 by ADMIN
Release LIB 2020.2.824
RichTextBox, GridView, TreeListView and ScheduleView handle [Ctrl + Tab] the same way as [Tab] and this way when they are inside Docking, the Navigator cannot open. These controls should not handle the Ctrl + Tab.  
Last Updated: 09 Apr 2020 14:58 by ADMIN
Release LIB 2020.1.406 (04/06/2020)

Application theme:

StyleManager.ApplicationTheme = new CrystalTheme();

Docking theme:

<telerik:RadDocking Grid.Row="2" telerik:StyleManager.Theme="Office2016">
	<telerik:RadDocking.DocumentHost >
				<telerik:RadPane Header="Description">
					<TextBlock TextWrapping="Wrap" Text="On the Documents tab above press Ctrl + Mouse Left button to display the Popup Menu. You can use the same combination on every tab."/>
	<telerik:RadSplitContainer InitialPosition="DockedBottom">
			<telerik:RadPane Header="NonDraggable">
				<TextBlock TextWrapping="Wrap" Text="This pane cannot be dragged, because it has its property CanFloat set 'False'."/>

Last Updated: 09 Mar 2020 08:49 by ADMIN
Release LIB 2020.1.309 (03/09/2020)
When a RadPaneGroup is not in the DocumentHost and it has only 1 RadPane, UI elements placed in that pane cannot be selected in the designer.
Last Updated: 03 Sep 2020 13:45 by ADMIN
Release LIB 2020.2.831 (08/31/2020)
The compass is misplaced on the second monitor when launching *.exe on monitors with higher DPI. The tool window also is not positioned correctly. 

  <application xmlns="urn:schemas-microsoft-com:asm.v3">
      <dpiAwareness xmlns="">PerMonitor</dpiAwareness>
      <dpiAware xmlns="">true</dpiAware>
Last Updated: 14 Feb 2020 08:00 by ADMIN
Release R1 2020 SP1
ToolWindow does not respect the "Show window contents while dragging" setting when it is first floated.
Last Updated: 10 Feb 2020 14:26 by ADMIN
Release R1 2020 SP1
Last Updated: 04 Oct 2019 10:28 by ADMIN
Release LIB 2019.3.1007
The CustomElementLoading event can't be canceled without creating a new instance of the custom element.

As a workaround in the CustomElementLoading event handler you can call the SetAffectedElement() with creating DependencyObject and then Cancel the event by setting the Cancel property.
private void RadDockingOnCustomElementLoading(object sender, LayoutSerializationCustomLoadingEventArgs e)
    if (e.CustomElementTypeName == "MyRadPane")
        e.SetAffectedElement(new DependencyObject());
        e.Cancel = true;              
Last Updated: 03 Jun 2019 06:26 by ADMIN
Release LIB 2019.2.603 (06/03/2019)
When the IsHidden property of a RadPane within a ToolWindow is set to True and then to false in quick succession, the ToolWindow is not shown. 

As a workaround, you can disable the animation of the ToolWindow:
<Style TargetType="telerik:ToolWindow">
<Setter Property="telerik:AnimationManager.IsAnimationEnabled" Value="False" />

The above style need to be placed in the resources of the App.xaml in order to take effect on the ToolWindows, since they are displayed in a separated visual tree.
Last Updated: 21 Oct 2019 10:53 by ADMIN
Release R3 2019 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,


Last Updated: 19 Apr 2019 14:05 by ADMIN
Release LIB 2019.1.422 (04/22/2019)
The exception is reproduced when multiple toolwindows with nested owners are floated and they are reloaded by re-merging the dictionaries in App.xaml in a NoXaml scenario.
Last Updated: 30 Oct 2019 07:49 by ADMIN
Release LIB 2019.3.1103
Last Updated: 08 Feb 2019 12:40 by ADMIN
When the RadDocking Items are reordered during runtime and new RadSplitContainers/RadPaneGroups are generated, the save/load behavior is sometimes incorrect. 
Last Updated: 19 Apr 2019 12:58 by ADMIN
Release LIB 2019.1.422 (04/22/2019)

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.

Last Updated: 29 Oct 2020 08:03 by ADMIN
Release LIB 2020.3.1102 (11/02/2020)
A possible workaround has been demonstrated in the attached project.
1 2 3 4 5