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!

Showing a ContextMenu inside the AutoHideArea causes it to be closed immediately.
If a TextBox inside the AutoHideArea is right clicked the AutoHideArea is closed.

Calling EnumeratePanes() after reordering RadPanes into a RadPaneGroup using drag and drop returns the panes in wrong other.This causes another issue. When saving the layout by using the SaveLayout method, the RadPanes are saved in wrong order.


For a workaround you can check the following thread: http://www.telerik.com/forums/panes-in-documenthost-not-saved-in-display-order 

"You can then fix the problem as follows:
    1. Read the RadPaneGroup.Items collection and extract the SerializationTag for each pane to a list. This list contains the correct order which you want to save.
    2. Save the docking layout using the SaveLayout() method on the main docking control and extract the XML as a string as you normally would. But do not save it to a file just yet.
    3. Create an XML document using XDocument and parse the XML string.
    4. Extract a list of all elements of type "RadDocumentPane" using the Descendants() method and sort these in the right order using the ordered list you created in step 1.
    5. Locate the RadPaneGroup for the DocumentHost and delete all elements of the child element "Items".
    6. Add the sorted elements from step 4 back into the RadPaneGroup.Items container.
    7. Save the result to a textfile."

Moving a ToolWindow when the DPI of the Window 7, 8 is higher then 100% causes incorrect offset to the mouse pointer to by applied. 

This issue leads to the following unexpected behaviors when ran under Window 8 OS:
When the:
- DragDropMode is set to Deferred. The compasses are not hidden after reorder.
- AllowDragReorder is set to True. In this scenario you should be able to reorder tabs without the need to float team. The incorrect offset causes them to be floated making it impossible to reorder tabs as expected.

Currently, you can drag and drop panes only in their parent RadDocking control. Allow dragging from one RadDocking to another.

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

This happens when primary monitor is with lower resolution. Maximize the pane on the primary monitor, then maximize it to the second monitor - the maximized state is incorrect.

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.

The flyout element is the popup that shows the current RadPane when when it is unpinned in the auto-hide area. Currently, the min width of the flyout is hard-coded to 50. Allow changing this value.

When DragDropMode is set to Deferred and Pane are moved around in the Docking control if the layout is saved and loaded some Panes are rendered incorrectly.

Available in LIB version 2016.2.516, it will be also available in the R2 2016 SP1 Release.

The same issue is observed when a WindowsFormsHost is placed inside RadPane. In that scenario the "made floating" animation of the RadPane instances is suppressed by the WindowsForms integration leading to flickering issues.

This issue is replicable in a setup which has two monitors and wit different DPI.
If a docking window is resized to a width over both monitors, when the window is more than a half on the monitor with lower DPI, it is not possible to dock it.