Unplanned
Last Updated: 03 Aug 2016 12:48 by Licensing
Initially HeaderDropDownMenu button is shown on window's caption bar of docked RadPanes but after undocking that button mysteriously disappears. The RadPane is still "Dockable" but for some reason there is no HeaderDropDownMenu button on it. This behavior leads to user confusion.
Unplanned
Last Updated: 10 Nov 2017 18:04 by ADMIN
Unplanned
Last Updated: 30 Oct 2017 15:02 by ADMIN
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.
Unplanned
Last Updated: 03 Jan 2017 21:09 by Licensing
This happens in particular scenario after saving/loading the layout.
Unplanned
Last Updated: 03 Jan 2017 21:19 by ADMIN
Setting TabStripPlacement should be possible not only for RadPaneGroups but for the entire RadDocking control. That TabStripPlacement value should be used as default value for all the auto generated RadPaneGroups.
Unplanned
Last Updated: 04 Aug 2016 14:58 by ADMIN
Place one RadPane in a RadPaneGroup. Bind IsHidden property of this RadPane, and set the default value to True. If you change it to False, the width of the AutoHide area is not set to the correct one.
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: 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: 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: 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: 28 Dec 2018 08:39 by ADMIN
The RadDocking control template hosts several AutoHideArea elements, one for each auto-hide placement - left, top, right, bottom. When you unpin a RadPane, it goes into one of those areas. The active auto-hide area where the pane will go is determined by the State of the topmost RadSplitContainer.

Allow manually setting the auto-hide area where the RadPane will go when unpinned.
Unplanned
Last Updated: 21 Nov 2018 16:55 by ADMIN
The RadPaneGroup inherits RadTabControl and the TabStripPlacement property. Currently the RadPaneGroup does not support setting this property as the corresponding ControlTemplates are not implemented.
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: 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: 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: 03 Jan 2017 20:55 by ADMIN
ADMIN
Created by: Georgi
Comments: 0
Category: Docking
Type: Feature Request
0

			
Unplanned
Last Updated: 03 Jan 2017 20:22 by ADMIN
Provide a sorted collection of the RadPane instances which would be activated by the built-in ActivationManager. 
This would make it possible to get the order of the currently shown ToolWindow instances.