Support the nesting of a RadDocking control in RadPane or other RadDocking control.
In the following scenario: Floating Pane's size has been changed. The layout has been saved. The layout has been loaded. The Pane has been docked. Making the Pane floating should retain the custom size from point 1.
Make it possible to set fixed WIdth/Height sizes to the PaneGroups. In the current version setting the Width/Height properties of the PaneGroup leads to incorrect placement of the groups while docked in the control. Available in the 2017 R2 Release. More information you can find here: http://docs.telerik.com/devtools/wpf/controls/raddocking/features/pane-groups#set-minmaxwidth-and-minmaxheight
As a user of the control I want to be able to write custom logic for saving and loading the layout of the Docking control so that - I can customize which elements should be saved (I want to exclude elements) - I can describe how the elements should be loaded - I can choose how the layout file is formatted - I can choose which properties of a RadSplitContainer, RadPaneGroup or RadPane are saved Available in the 2016 R2 release.
Show a navigation window for navigating between panes when the user presses Ctrl+tab. RadDock for WinForms has such feature: https://docs.telerik.com/devtools/winforms/dock/architecture-and-features/quick-navigator
Closing a RadPane in the DocumentHost should focus the last selected pane instead of the first one(as in VS)
Yes please!
Add shortcuts like: - close a pane by mousewheel click on the tab - close the active pane by keyboard shortcut (e.g. Ctrl + W) - switch active pane by Ctrl + Tab
As a user of the control I want to be able to write custom logic for saving and loading the layout of the Docking control so that - I can customize which elements should be saved (I want to exclude elements) - I can describe how the elements should be loaded - I can choose how the layout file is formatted - I can choose which properties of a RadSplitContainer, RadPaneGroup or RadPane are saved Available in the 2016 R2 release.
Add overloads for LoadLayout and SaveLayout methods of the Docking control with parameter of type XElement instead of Stream. Change the Save/Load layout code to use LinqToXML instead of XmlReader and XmlWriter.
When you create a custom PaneGroup by adding a class that inherits RadPaneGroup make it possible that the built-in Save/Load layout functionality loads those PaneGroups. Available in the 2016 R2 release.
Available in LIB version 2015.2.817, it will be also available in the 2015 Q3 Release.
It would be great to be able to use other Resources other that the App.xaml for the Styles applied to the ToolWindow instances. As they are automatically created and as expected are in a different visual tree accessing for example the Resources of the MainWindow is not possible. Available in the 2016 Q1 SP1 Release.
Currently, the RadPaneGroup has one Grid layout with Margin="5" present in its control template, which causes the Content of each child pane to be indented according to the Margin property's value.
To work this around, extract the control template, with x:Key="RadPaneGroupDocumentHostControlTemplate", and modify the Grid layout, which has its Margin property set to 5. After that, create a new style with TargetType="RadPaneGroup" and set its DocumentHostTemplate property, to the modified one.
Open a Window from a button placed inside the unpinned pane. The pane does not hide and the window is shown below it.
It would be useful to be able to customize the properties of the auto generated RadSplitContainer, RadPaneGroup and ToolWindow instances (created by floating, docking, pinning and unpinning of RadPane instances) based on the old RadPane instance. For example the GeneratedItemsFactory methods could provide information about the RadPane for which SplitContainer etc is created. Available in the 2016 R2 release.