Last Updated: 08 Apr 2024 14:24 by ADMIN
Release 2024.1.408

This happens because in the current version of Telerik, the IsTopmost of the ToolWindow that host the floating pane is set to True. That was needed for a related new functionality, but it brings a major behavioral change in the RadDocking control.

To work this around, you can subscribe to the ToolWindowCreated event of RadDocking and set the IsTopmost property of the creating ToolWindow to False.

private void RadDocking_ToolWindowCreated(object sender, Telerik.Windows.Controls.Docking.ElementCreatedEventArgs e)
    var window = (ToolWindow)e.CreatedElement;
    window.IsTopmost = false;

Last Updated: 25 Jan 2024 19:04 by ADMIN
Release LIB 2023.3.1315 (15 Jan 2024)
When a RadSplitContainer's Orientation is set to Vertical and a RadPaneGroup has a Margin with negative values for the Top and Bottom properties, the container may appear cropped.
Last Updated: 15 Jan 2024 11:23 by ADMIN

In OS two monitors are configured: monitor 1 (3840x2160) scale: 200% and monitor 2 (1920x1200) scale 100%.

Our wpf application has a main window, maximized on screen 1 and a child window maximized on screen 2.

In the app.manifest we use per monitor dpi awareness:

<application xmlns="urn:schemas-microsoft-com:asm.v3">
    <dpiAware xmlns="">True/PM</dpiAware>
    <dpiAwareness xmlns="">PerMonitorV2,PerMonitor</dpiAwareness>

Both windows have a RadDocking instance with a docked RadPane like:

  <telerikDocking:RadDocking Name="Docking"                              
    <telerik:RadSplitContainer InitialPosition="DockedBottom">
        <telerik:RadPane Header="Test Panel" IsDockable="True">
          <Border Background="Green">
            <TextBlock Text="Test Panel" HorizontalAlignment="Center" VerticalAlignment="Center"/>


If you drag and move the docked panel from screen 2 to screen 1 the compass at screen 1 is only shown if the mouse position is in the first quadrant of screen 1 . The compass is shown on the correct place but cannot be activated, so that no dropping is possible.

Without unsing per monitor dpi awareness everything works fine. Unfortunately we must use per monitor dpi awareness for our application.

This bug is also reproducable in V2023.3.1218.

Last Updated: 18 Dec 2023 06:53 by ADMIN
Release LIB 2023.3.1218 (18 Dec 2023)
The drag-and-drop logic currently expects the different RadDocking instances to be hosted in one Window element, more specifically, in the MainWindow of the application.

We could add support for different instances being hosted in separate Window elements that will support dragging and dropping operations.
Last Updated: 18 Dec 2023 06:53 by ADMIN
Release LIB 2023.3.1218 (18 Dec 2023)
Having only a single RadPane in one RadDocking instance will not allow you to drag it into another RadDocking instance, which does not have any elements when both RadDocking instances are under the same drag-drop domain.
Last Updated: 15 Aug 2023 13:39 by ADMIN
Release LIB 2023.2.821 (21 Aug 2023)

When a RadSplitContainer with Orientation="Vertical" contains RadPaneGroup instances, resizing them causes a flicker when the ShowResizePreview property is set to False. This happens with the VisualStudio2019 theme.

For the time being, a possible workaround is to create a global Style with TargetType="RadPaneGroup" and set the Margin property to "0":

<Style TargetType="telerik:RadPaneGroup" BasedOn="{StaticResource RadPaneGroupStyle}">
    <Setter Property="Margin" Value="0"/>

Last Updated: 31 Jul 2023 12:49 by ADMIN
Release LIB 2023.2.724 (24 Jul 2023)
 NullReferenceException when dragging a window outside the control (see the attached video).
Last Updated: 07 Jul 2023 05:44 by ADMIN
Release R2 2023 SP1
Updating the ThemeSizeHelper by incorporating the margins of GridSplitters and AutoHide areas would significantly improve the flexibility and convenience of better switching between Windows 11 and Windows 11 Compact themes within the RadDocking control.
Last Updated: 12 Jun 2023 13:21 by Martin Ivanov
Currently, if the RadPaneGroup contains only a single RadPane, its header is not displayed on the bottom of the control. Instead, you see it only in the Title area of the group.
Add mode that allows to keep the header of the pane at the bottom when there is only a single RadPane element.
Last Updated: 29 May 2023 10:03 by ADMIN
Release R2 2023
Created by: Martin Ivanov
Comments: 0
Category: Docking
Type: Feature Request
Currently, you can drag and drop panes only in their parent RadDocking control. Allow dragging from one RadDocking to another.
Last Updated: 07 Apr 2023 07:56 by ADMIN
Release LIB 2023.1.407 (7 Apr 2023)

The DataContext of RadPane's content is lost when showing its preview in the DockingNavigator.

As a workaround, you could set the DataContext of the content element could be set explicitly.

Last Updated: 02 Mar 2023 13:25 by Martin Ivanov
Created by: Martin Ivanov
Comments: 0
Category: Docking
Type: Feature Request
Allow defining an additional "preview" tab that is shown at the right most part of the tabstrip area. This tab should have a special highlighting like faded tab header or a different background. This is similar to the Visual Studio preview tab that is displayed when you use the Go to Definition (F12) function on an API name. Usually you have a single preview tab.
Last Updated: 19 Jan 2023 14:50 by ADMIN
Loading the layout does not set the size of the ToolWindow created for a floating-only pane.
Last Updated: 23 Dec 2022 15:25 by Stenly
Currently, the GridSplitter used for resizing an unpinned pane disappears after a certain threshold. We could include an option for it to not disappear.
Last Updated: 25 Nov 2022 06:16 by ADMIN
Release LIB 2022.3.1128 (28 Nov 2022)

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.

Won't Fix
Last Updated: 06 Oct 2022 09:20 by ADMIN
Created by: Martin Ivanov
Comments: 1
Category: Docking
Type: Bug Report
A memory leak related to the automation peers of the RadPane and RadPaneGroup appears when you close a pane (using its Close button) even if you call its RemoveFromParent() method.

To work this around disable the automation peers. To do so please set the static AutomationManager.AutomationMode property toAutomationMode.Disabled.
public MainWindow()
    AutomationManager.AutomationMode = AutomationMode.Disabled;

The issue originates from ItemsControlAutomationPeer. It is reported to Microsoft in their old connect portal here =>
Last Updated: 30 Sep 2022 11:59 by ADMIN
Release LIB 2022.3.1003(3 Oct 2022)
Resizing a dynamically added group results in a change of other groups' sizes, if the original groups were previously resized as well.
Last Updated: 15 Sep 2022 08:14 by ADMIN
Release LIB 2022.3.919 (19 Sep 2022)
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.
Last Updated: 09 Aug 2022 19:45 by ADMIN
Release LIB 2022.2.815 (15 August 2022)
This issue is replicable in a setup which has two monitors and wit different DPI.
If a docking window is resized to a width over both monitors, when the window is more than a half on the monitor with lower DPI, it is not possible to dock it.
Last Updated: 02 Aug 2022 07:29 by Martin Ivanov
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).
1 2 3 4 5 6