Unplanned
Last Updated: 19 Aug 2024 14:10 by Martin Ivanov

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

Unplanned
Last Updated: 12 Aug 2024 13:46 by Stenly
A System.ArgumentException: 'Width must be non-negative.' exception is raised when resizing two RadPaneGroup instances from a single RadSplitContainer when the ShowResizePreviuew of RadDocking is set to False.
Completed
Last Updated: 07 Aug 2024 08:11 by ADMIN
Release 2024.3.806 (2024 Q3)
Saving and loading a minimized ToolWindow causes the elements inside RadDocking to not behave as expected. For example, dragging a pane may not visualize the ToolWindow, or selecting a pane may not mark it as active/selected.
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.
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: 10 May 2024 06:17 by Stenly
Add API to specify the minimum width and height of the DocumentHost element.
Unplanned
Last Updated: 29 Apr 2024 13:33 by Erica
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.
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;
}

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: 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: 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: 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"/>
</Style>

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: 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.
Unplanned
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.
Completed
Last Updated: 29 May 2023 10:03 by ADMIN
Release R2 2023
Created by: Martin Ivanov
Comments: 0
Category: Docking
Type: Feature Request
9
Currently, you can drag and drop panes only in their parent RadDocking control. Allow dragging from one RadDocking to another.
Completed
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.

Unplanned
Last Updated: 02 Mar 2023 13:25 by Martin Ivanov
Created by: Martin Ivanov
Comments: 0
Category: Docking
Type: Feature Request
3
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.
Completed
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.
1 2 3 4 5 6