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.

Description: for example if we have two auto-hidden Tool windows (left and right), first click on the right one but don't pin it, then click on the left one (don't pin it also) and you will notice that for a fraction of time its caption displays the text of the previous window. Then you can click the right window again and you'll see the opposite effect. This tiny fraction of time raises to a significant period of time when tool windows are loaded with multiple controls. AutoHideWindowDisplaying event fires before ActiveWindowChanged event (AutoHideTabStrip.ActiveWindow is the other tool window during AutoHideWindowDisplaying). That is why for a fraction of time (during AutoHideWindowDisplaying event) you can see different caption text. To reproduce: - add RadDock - add two auto-hidden Tool windows (left and right) - first click the right one in order to display the hidden tool window -> for a fraction of time its caption is for the other tool window Workaround: private void radDock1_AutoHideWindowDisplaying(object sender, AutoHideWindowDisplayingEventArgs e) { AutoHideTabStrip autoHide = e.NewWindow.DockTabStrip as AutoHideTabStrip; if (autoHide != null) { autoHide.ActiveWindow.Text = e.DockWindow.Text; } }

Another possibility to reduce the flicker is to stop the animations: 

radDock1.AutoHideAnimation = AutoHideAnimateMode.None;

To reproduce: 

Follow these steps:

1. Extract the project I have attached and open it in Visual Studio.
2. Run it.
2a. You should note two docked windows on the left (tabbed).
3. Click on the "Open Next Window" button.  The first two clicks will simple open the first two docking windows (already open)
On the 3rd click another docking window should appear on the right.
Click the button a couple more times.  You should have 3 docked windows on the right.
4. Now, drag the windows on the left so they are floating and docked together.
5. Click on the Save Layout button at the bottom.
6. Close and rerun the sample.
You should note that the floating windows appear at the expected location.  Move them off to the side away from their default location (away from the center of the screen)
So far so good.
7. Upon reopening the application with toolWindow3, 4 and 5 floating and docked close the floating window.
8. Save the layout.
--> This is where the key is...
9. Close and rerun the sample.
If you watch quickly you'll see several windows "flicker".  They appear and disappear quickly.
Now, if you hit the "Open Next Window" button 5x, it will open the first two (already open) and then open the 3rd, 4th and 5th windows.  But NOTE - they are NOT docked together.  They are also not at the location where you left them (remember you needed to move them to the side)

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--;          
}

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.

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;

RadDock - implement BackgroundImage property.

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

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.

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

The issue could be observed in a scenario with nested RadDock controls. An exception is received when the window state is changed to AutoHide.

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;

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.

To reproduce:
- Add several tool windows to RadDock.
- Make a window floating and then dock it back.
- Hide all windows and then save the layout.
- Close the application.
- Start the application and load the saved layout.
- Show all windows again.

To reproduce:
- Add a panel to a form, dock it to fill the entire space.
- Add RadDock to it, set its Dock property to fill.
- Add a document window with a grid to it (the grid should fill the entire space).
- Start the application and maximize the form.  

Workaround:
- Remove the panel or use RadPanel instead.

- Handle the SizeChanged event
private void RadForm1_SizeChanged(object sender, EventArgs e)
{
	var window = this.radDock1.ActiveWindow;
	this.radDock1.ActiveWindow = null;
	this.radDock1.ActiveWindow = window;
}

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.

In the test scenario the Autohide Windows is hosted in parent RadDock floating windows.

The ToolWindow in AutoHide dockstate disposed,
after docking the main ToolWindow to tab mode, in a specific scenario.

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

The expected behavior should be similar to Visual Studio, once a maximized floating window starts being dragged it should go to a normal state so that the window under it is visible.

How to reproduce: just maximize a floating window, then start dragging it from the title bar, the docking guides will appear which do not help much since the window is still maximized.

Workaround: handle the Starting event of the DragDropService and change the WindowState of the window
public partial class Form1 : Form
{
    public Form1()
    {
        InitializeComponent();
        
        DragDropService service = this.radDock1.GetService<DragDropService>();
        service.Starting += Service_Starting;
    }

    private void Service_Starting(object sender, StateServiceStartingEventArgs e)
    {
        FloatingWindow fw = e.Context as FloatingWindow;
        if (fw != null && fw.WindowState == FormWindowState.Maximized)
        {
            fw.WindowState = FormWindowState.Normal;
            fw.Location = new Point(Cursor.Position.X - fw.Size.Width / 2, Cursor.Position.Y);
        }
    }
}