Completed
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).
Completed
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.
Completed
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.
Completed
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.
Unplanned
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">
  <windowsSettings>
    <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">True/PM</dpiAware>
    <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2,PerMonitor</dpiAwareness>
  </windowsSettings>
</application>


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


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

 

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.

Completed
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;
}

Unplanned
Last Updated: 11 Mar 2025 12:42 by Petar
Docking A1 is nested in parent Dockin A, they share equal DragDropGroup Name so that drag drop is enabled between them. Droping pane from A1 to center of A's  dragdrop compass, then switching panes results in unexpected opened tool window. Dragging this window results in NullReferenceException.
Unplanned
Last Updated: 10 Jun 2024 10:47 by ADMIN

I need a behaior for RadPane like this:

 

When we have onl one RadPane, then show headr with a full RadPane group width (Which can be achived using PaneHeader)

In opposite - use regular tab style

Also if I undock RadPane to ToolWindow and I have only single item, I want to completely hide tabs/headers

All this should work for Top TabStripPlacement

 

Unplanned
Last Updated: 11 Jun 2024 07:32 by Martin Ivanov
Raise the PropertyChanged event for the IsInToolWindow property of RadPaneGroup. Consider doing this also for the other elements that expose this property.
This is useful when you need to know when the group is moved in and out of ToolWindow. For example, when using triggers or data bindings to customize the behavior of the group.
Completed
Last Updated: 11 Feb 2025 07:40 by ADMIN
Release 2025.1.211 (2025 Q1)

If you drag the pane from one RadDocking element to another, the ActivePane of the docking that started the drag operation is not cleared. The ActivePane should be updated (set to null, or updated in accordance to the PaneActivationMode setting) because the corresponding pane is no longer in this RadDocking instance.

To work this around, you can subscribe to and manually update the ActivePane property.

   private void RadDocking_LayoutChangeEnded(object? sender, EventArgs e)
    {
        var docking = (RadDocking)sender;
        if (docking.ActivePane != null && !docking.Panes.OfType<RadPane>().Contains(docking.ActivePane))
        {
            docking.ActivePane = null;
        }
    }

Duplicated
Last Updated: 27 Nov 2024 16:54 by ADMIN
Created by: Frank
Comments: 1
Category: Docking
Type: Bug Report
0

In a multi monitor scenario with different scalings and an application that is configured to run ‚per monitor dpi awareness‘ a floating toolwindow cannot be docked at all positions.

Example:

Monitor 1: 1920 x 1200 (100%), Monitor 2: 2048 x 2560 (150%)

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.

Both windows have a RadDocking instance with a docked RadPane. Start the application, undock a tool window and try to dock it at the right position on monitor 1.

è It is not possible since the compass is deactivated before the mouse cursor reaches the right monitor area.