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: 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.
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.

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.
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.
Unplanned
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.
Unplanned
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).
Unplanned
Last Updated: 12 Jul 2022 07:56 by Stenly
We could improve the drag-drop functionality of the RadDocking control when the FlowDirection="RightToLeft".
Unplanned
Last Updated: 04 Jul 2022 10:51 by Martin Ivanov
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.
Unplanned
Last Updated: 29 Dec 2021 14:48 by ADMIN
Add a visual element to display the exact drop location of an item, when reordering panes in a pane group.
Unplanned
Last Updated: 21 Oct 2021 13:21 by ADMIN
Created by: Julien
Comments: 0
Category: Docking
Type: Feature Request
1
Allow floating panes from the auto-hide area as this can be done from a pinned RadPaneGroup.
Unplanned
Last Updated: 08 Dec 2020 11:54 by ADMIN

Hi,

 

In most docking applications (Telerik WinForms, Visual Studio), it is possible to right click on the pane-tab header and get the options:

- New Horizontal Tab Group

- New Vertical Tab Group

- Move to Next Tab Group 

etc.

 

This would nice in WPF as well

 

/Brian

 

 

Unplanned
Last Updated: 09 Sep 2020 09:12 by ADMIN
A property can be exposed to control the Width/Height of the RadGridResizers between the different elements and their respective Margins.
Unplanned
Last Updated: 25 Mar 2020 09:58 by ADMIN
Currently the CloseButtonPosition property of the RadDocking only takes effect when a RadPaneGroup is inside the DocumentHost. We can introduce a way to place the close button in the pane when a group is outside the DocumentHost (for example in a ToolWindow).
Unplanned
Last Updated: 13 Feb 2020 10:06 by ADMIN
Created by: Christian
Comments: 0
Category: Docking
Type: Feature Request
4
Currently, unpinned panes need to first be pinned in order to be floated. Floating of unpinned panes should be made possible.
Unplanned
Last Updated: 03 Dec 2019 14:47 by ADMIN
Prevent the closing of the auto-hide area if the context menu of an element in it is opened.
Unplanned
Last Updated: 01 Nov 2019 09:21 by ADMIN

This feature request is related to Ticket 1435779

 

Image for context

 

Currently, there's no support for increasing the drag threshold for the items on the orange box. Even after setting the values below.

DragDropManager.MinimumHorizontalDragDistance = 5000;
DragDropManager.MinimumVerticalDragDistance = 5000;

 

It would also be beneficial if instead of just relying on the drag threshold which is the box. Add a support for a sort of "Drag Time" concept where we can define how long the user should've held the actual pane before dragging/going outside the threshold.

1 2 3 4 5