Completed
Last Updated: 17 May 2021 09:54 by ADMIN
Release LIB 2021.2.517
The dropdown menu in the DocumentHost throws a NullReferenceException in newer themes when it is opened.
Completed
Last Updated: 20 Oct 2021 07:13 by ADMIN
Release LIB 2021.3.1025 (25 Oct 2021)
Office2019 theme does not remove the ScrollViewerElement element when CanUserClose is set to False and the Visibility is set to Collapsed on a DocumentPane.
Unplanned
Last Updated: 03 Jan 2017 20:33 by ADMIN
Regions in panes content are not resolved when the pane is unpinned and collapsed. This happens only when you change the regions in runtime while the pane is unpinned and collapsed.
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

 

Declined
Last Updated: 23 Apr 2015 15:14 by ADMIN
Panes that are autohidden are cut if resized too much - this is due to limitation in WPF that popups should not cover more than 75% of the screen.
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;
}

Declined
Last Updated: 29 Jun 2015 16:23 by ADMIN
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: 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.
Declined
Last Updated: 05 Jan 2017 15:23 by ADMIN
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.
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: 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).
Won't Fix
Last Updated: 06 Jul 2015 11:45 by ADMIN
The PaneHeader is shown and then immediately collapsed. 

Setting the PaneHeader to null can be used as a workaround if the project uses the default theme.
Completed
Last Updated: 11 Feb 2014 10:23 by ADMIN
When Saving and Loading a layout which has empty DocumentHost an ArgumentOutOfRangeException is thrown
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.
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.