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.

IMPROVE: RadDock - currently when middle click is executed the ActiveWIndows closes instead of the clicked one

Steps to reproduce:
1. Add a new form to a project and set MdiContainer to true
2. Drag a RadDock onto the form and set the AutoDetectMdiChildren to true
3. Add another form to be used as MdiChild
4. Drag a button onto the second form and in the Click event handler add call to this.Close()
5. Run the project and add an MdiChild form to the MdiContainer form.
6. Press the button on the child form. You will see an exception.

FIX. RadDock - with two nested docks, setting the DocumentTabsAlignment of the other dock automatically sets the same on the inner one and this cannot be changed. Once you change it and reload the design time, its setting is being reset.

To reproduce 
- add RadDock with couple DocumenWindows in it
- add second RadDock with coupld DocumentWindows in it, in one of the windows of the first dock
- set Raddock2 DoumentTabsAlignment to top
- set DocumentTabStrip2 TabStripAlignment also to top or default
- drag a radbutton into documentwindow3 and double click it, to get a click event
- go into code view and remove the created event manually
- change back to form view. the alignment in DocumentTabStrip2 has been automatically changed to bottom

We have a somewhat complicated application in which we have a RadDock inside another RadDock.
Everything seems to work just fine, with one exception.

When we resize the application window itself, the ToolWindow and DocumentWindow controls don't properly redraw their areas..

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

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

1. Create a new project containing RadDock
2. Add two buttons, the first one will add a document window, the second one will remove it.
3. Run the project and add and remove document windows multiple times.

as magnetic behaviour I mean that when you move a window close to another window, the first window just snap to the other. The same behaviour is fine when you resize a window.
The magnetic behaviour helps you to arrange floating windows into the screen, so people dont get crazy trying to align and resize all the floating windows around in the screen.

RadDock's layout does not handle correctly changed Windows DPI settings.

When you have an AutoHideTab docked to right and you want to show an image and horizontal text,
the text is cut off taking the width of the image.

If you have a RadDock with child form in an MDI scenario, and you swtich between the tabs of the hosted forms, the Activated event of these forms will not be fired.

ActiveWindowChanged cannot be canceled if the event is fired for the case where you switch from one tab of a ToolWindow to another tab of a ToolWindow

Hidden HostWindows are not loaded correctly when the load operation is performed twice.

Would be useful to have the option to create the tab close button theme which depends on the states of the button's containing tab.

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

When the RadDiock is in right to left mode and the QuickNavigator is shown. The snapshot in the QuickNavigator is of the top-left corner of the window in the current context. The snapshot should display the top-right corner.

FIX. RadDock - arranging DocumentWindows tabs in design time is not possible.

When reducing the size of a right-docked auto-hide tool window it goes out of the area of the RadDock