support of Pin tab operation in DocumentContainer of RadDock

Currently, it is not possible to add any RadElement to a TabStripItem in DocumentTabStrip.

Resolution: 
Use the static class RadDockEvents to subscribe to events before InitializeComponent

The DocumentTabStrip raises the SelectedIndexChanging event twice

Detailed description in forum thread: http://www.telerik.com/community/forums/winforms/dock/closing-last-window-with-middle-clicking-the-document-tab-throws-an-exception.aspx

I am using nested dock objects. I find that if I close one tabbed window using the X icon, the control closes properly, leaving the other tabbed windows opened. However, if I try to close the tabbed window using the keyboard sequence Ctrl+F4, this also closes one of the tabs within another window!
I have attached an example form. This contains a RadDock with 2 windows, DocumentWindow1 and DocumentWindow2. DocumentWindow1 also contains two document windows, DocumentWindow3 and DocumentWindow4. The sequence of events to reproduce this behaviour is as follows:
- In designer mode: set focus on DocumentWindow2 and Save
- Run app
- Form opens with focus set on DocumentWindow2, as expected
- Set focus on DocumentWindow1
- Set focus back to DocumentWindow2
- Press Ctrl+F4 to close DocumentWindow2
- This closes DocumentWindow2 but also closes DocumentWindow4 within DocumentWindow1.
Please note that if I use the X button to close DocumentWindow2, only DocumentWindow2 gets closed, as expected.

I've discovered a behavioral issue with the tool-window when one of its containing control's data-binding is updated.

I'm designing an application using the MVVM design pattern with a basic View and View-Model. The View is a form that contains a RadDock, ToolWindow containing a Label, and a Button to update the Label's Text; and data-binding setup to the ToolWindow's property "DockState" and a Label's property "Text". The View-Model contains the bound properties "ToolWindow1DockState" and "Label1Text", which implements INotifyPropertyChanged to update the respective controls; and a method used to update Label1's text.

After I click "Auto-hide" on ToolWindow1 and click the "Change Text" button, I'm expecting ToolWindow1 to remain in the Auto-hide state. Instead, ToolWindow1 is placed in the Docked state.

I have issues with Databindings for RadToggleButton and RadDock ToolWindow.

Here are 3 scenarios to try with my repro application.

ToggleButton
Click the radToggleButtonElement1, notice that the binding never occurs.

ToolWindow Docking issue 1
Dock the toolWindow1 to the left over ToolWindow2
Click toolWindow2
Click toolWindow1
Click toolWindow2
Notice each time you click another tool window, the binding is triggered even if the property value hasn't changed.

ToolWindow Dockin issue 2
Dock the toolWindow1 to the left over toolWindow2
Notice that the binding is triggered, but with the previous value (Floating instead of Docked)
close the toolWindow1
Notice that the binding is triggered, but with the previous value (Docked instead of Hidden)

MDIChildren of RadDock hosted in HostWindow not serialize DockType property equal to 'Document' in this case and loaded like ToolWindow

1) Start with new Forms application.

2) Add RadDock set to Fill to the Form.

3) Open Designer.

4) Add ToolWindows docked Top and Right.  Add two ToolWindows docked fill.

5) Close Designer.

6) Open Designer.

7) Delete two docked ToolWindows.

8) Close Designer.

9) Deleted ToolWindows remain.  I also had them become tabbed with the 
ToolWindow docked to the Top in a previous test.

10) In the Designer, if I check the box, the two ToolWindows become docked
Left.  If I close the Designer and re-open it, I can then delete them.

11) I deleted all ToolWindows in the Designer and closed it.

12) The ToolWindows are removed.

13) Upon re-opening the Designer and adding windows, they do not appear
upon closing the Designer.

14) It appears that the documentContainer is missing from the DocumentOutline.
However, it is still present in the code because if I delete the RadDock, and
then re-add it, the name of the new documentContainer is numbered higher than
the first one.  If I try to rename it from 1 to 3, it tells me that 1 is still
in use.

15) Adding ToolWindows at this point works again.

Issue wirh loading layout from xml related to disposing mechanism in RadDock

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.