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.

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.

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.

A memory leak related to the automation peers of the RadPane and RadPaneGroup appears when you close a pane (using its Close button) even if you call its RemoveFromParent() method.

To work this around disable the automation peers. To do so please set the static AutomationManager.AutomationMode property toAutomationMode.Disabled.

The issue originates from ItemsControlAutomationPeer. It is reported to Microsoft in their old connect portal here =>

https://connect.microsoft.com/VisualStudio/feedback/details/838165/memory-leak-in-the-itemscontrolautomationpeer-because-items-removed-from-the-itemscollection-are-still-strongly-held-by-the-weakrefelementproxystorage

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.

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.

Available in LIB version 2016.3.1003, it will be also available in the R3 2016 SP1 Release.

Changing theme runtime when we have a floating RadPane, then dock it into one of the sides of an already docked RadPane and no splitter will show between them. Happens with implicit theming as well.

Possible work-around of this problem:

private void RadDocking_ElementLoaded ( object sender, LayoutSerializationEventArgs e )
 {
     if ( e.AffectedElement is RadPaneGroup )
     {
         var PaneGroup = e.AffectedElement as RadPaneGroup;
         var Panes = PaneGroup.EnumeratePanes().ToList();
         var SelectedIndex = PaneGroup.SelectedIndex;

         for ( int Index = 0; Index < Panes.Count; Index++ )
         {
             if ( ( Panes[ Index ].IsHidden || !Panes[ Index ].IsPinned ) && Index <= SelectedIndex )
             {
                 SelectedIndex++;
             }
         }

         PaneGroup.SelectedIndex = SelectedIndex;
     }
 }

The AutoHide area is closing when clicking at WinForms control placed in it.
The issue also can be reproduced with WebBrowser or any object of MarshalByRefObject type placed in the AutoHideArea.

Place a notepad over the MainWindow and mouseover an unpinned pane - the autohide area shouldn't show up.

When the Dock's auto-hide area is is about to be shown on two monitors simultaneously it is shown only on one of the monitors.

With three split containers in one other and no document host resizing between the first and second containers causes the first and third containers to resize, instead of the first and second containers.

After upgrading to Telerik WPF 2019.1.116 from 2018.3.1010 we receive a lot of:

System.ComponentModel.Win32Exception (0x80004005): Invalid window handle
   MS.Win32.UnsafeNativeMethods.GetWindowText(HandleRef hWnd, StringBuilder lpString, Int32 nMaxCount)

Exceptions. It makes out application very slow.

In version 2018 everyting was OK. See attached scerenshots.