The problematic tool window has a user control that is docked to fill and it is built entirely with Telerik controls. The dock control, tab strips, windows and even the controls inside the user control are correctly scaled. The issue comes when you start undocking and then docking the tool window. The size of the user control increases with each operation. The controls have anchors and although they have correct scaling they get stretched. This results in messed layout. 

The DocumentTabStrip and ToolTabStrip are created dynamically and when they initialize they call their Scale method. The tool window, the user control, and also all other controls added to it are created only once. When you undock the window a new tab strip is created and the existing controls are added to it. When we load the tab strip we call PerformRadAutoScale which calls the stip's Scale method. Calling Scale propagates to the child controls causing additional scaling to the Microsoft controls. RadControls don't have issues because we have logic to check the scaling of the window and we don't allow double scaling.

As a workaround, we can create custom tab strips and override the ScaleChildren property to return false.

this.radDock1.DockTabStripNeeded += this.RadDock1_DockTabStripNeeded;
private void RadDock1_DockTabStripNeeded(object sender, DockTabStripNeededEventArgs e)
{
    if (e.DockType == DockType.ToolWindow)
    {
        e.Strip = new MyToolTabStrip();
    }
    else
    {
        e.Strip = new MyDocumentTabStrip();
    }
}

public class MyToolTabStrip : ToolTabStrip
{
    protected override bool ScaleChildren => false;
}

public class MyDocumentTabStrip : DocumentTabStrip
{
    protected override bool ScaleChildren => false;
}

A nice addition to the existing RadDock implementation for re-docking floating windows will be the ability to re-dock floating windows to documents if the previous state of the floating window was a document window.

RadDock should support a MDI mode where the child mdi forms are displayed in the old fashioned way.

A user should be able to scroll to a desired item (window) by selecting it from the overflow menu. Currently, the selected item is inserted at the first position and the order of items is changed.

If we set the AutoHideSize of a ToolWindow to the RadDock size, upon opening the AutoHide window we will notice that there is a gap of about 20px between the edge of RadDock and the AutoHide window.

Let's have a ToolWindow in a RadDock. Float the ToolWindow and then close the FloatingWindow.
Save the layout, close the application and start it again. Load the layout and display the hidden ToolWindow by calling the DisplayWindow method. The ToolWindow will become docked instead of floating.

After a very specific sequence of steps, you may end up with an xml file of the RadDock layout that contains two windows, although there is only one window at the time the xml file is saved. In addition, when a floating window is loaded, it needs a click in order to get a caption string at the titlebar.

When you have a big UserControl in a DocumentWindow and you scroll down this UC, the UC is prescrolled when you try to set the focus on a control of the UC.

If you have a ToolWindow in AutoHide mode with a RadDropDownList in it and you choose an item from the list or scroll the items in the list, the ToolWindow will hide itself.

OnActivated is fired before OnLoad in forms which have RadDock instances. However, OnLoad should be fired before OnActivated.

Let's have a TextBox, ToolTip and a FloatingWindow containing the TextBox. The following code snippet will not show a tooltip for the textbox:
            this.toolTip1.ToolTipTitle = "ToolTip";  
            string strToolTip = "Exemple";  
            this.toolTip1.SetToolTip(textBox1, strToolTip);  
            this.toolTip1.AutoPopDelay = 32767; 
            this.toolTip1.Active = true;

Steps to reproduce: 
1. Add a RadDock to a form 
2. Add a document window
3. Add a button to the form and upon click add a user control to the document with Dock set to FIll 
4. Run the project and click the button. 
5. You will notice that the user control will not fill the parent container properly.

RadDock - implement BackgroundImage property.

RadDock - when loading layout, the control reads the stream from the current position instead from the beginning of it. This lead to exception "Root element is missing".

Steps to reproduce:

Dim strmDock As New MemoryStream

RadDock1.SaveToXml(strmDock)
RadDock1.LoadFromXml(strmDock)


Work around:
stream.Position = 0;

To reproduce:
- Create a MDI application with a RadDock in the mainform.
- Add docked to the left ToolWindow to the dock.
- On a button click add a child form with a RadDateTimePicker in it.
- Set the picker Dock property to Top.

Workaround: 
- Use the following SizeChanged event handler:
 private void RadForm1_SizeChanged(object sender, EventArgs e)
{
    this.rdMain.Width++;
    this.rdMain.Width--;          
}

When you place RadDock with AutoHideAnimation set to None, add several auto-hide windows and you switch between them, you will notice a flickering at the moment of the change.

The exception occures when the parent form is minimized.

The AutoHide popup is not shown in the scenario, demonstrated in the attached to the forum thread project.

When the DockWindowClosing event is fired, the ActiveWindow has already been changed.

The keyboard shortcuts should be executed according to the active RadDock control.