Create a new project and add RadForm
Add RadDock and set its Dock property to Fill
Run the project and start resizing the form, you will see that the memory increases

When saving the layout RadDock saves the windows as they appear in the DockWindows collection. However, improvement to save the current toolwindows position will be great addition.

If you change the name of a child mdi form in its Load event, this title will not be reflected by the tab of the document window created to host the child form.

General Information:
- works until 2012.2.726.00 Q2 2012 SP1 version of our controls
- does not work after 2012.3.1017.00 Q3 2012 version of our controls

Steps to reproduce:
1) Add RadDock control
2) Show Next and Previous Buttons of the default DocumentTabStrip:

        private void Form1_Load(object sender, EventArgs e)
        {
            this.radDock1.DockTabStripNeeded += new DockTabStripNeededEventHandler(radDock1_DockTabStripNeeded);
            
            tabStrip = this.radDock1.GetDefaultDocumentTabStrip(false);
            tabStrip.TabStripElement.StripButtons = StripViewButtons.All;
            DockLayoutPanel dockPanel = tabStrip.RootElement.Children[0].Children[3] as DockLayoutPanel;
            if(dockPanel != null)    
            {
                dockPanel.ZIndex = -1;
            }
            StripViewItemContainer stripContainer = tabStrip.TabStripElement.Children[0] as StripViewItemContainer;
            if (stripContainer != null)
            {
                stripContainer.Padding = new Padding(stripContainer.Padding.Left, stripContainer.Padding.Top, 0, stripContainer.Padding.Bottom);
            }
        }

        void radDock1_DockTabStripNeeded(object sender, DockTabStripNeededEventArgs e)
        {
            if(e.DockType == DockType.Document)
            {
                e.Strip = new CustomDocumentTabStrip();
            }
        }            

Expected Result: Navigate through all document windows by using the Next and Previous Button beside OverflowDropdownButton
Actual Result: NullReferenceException unhandled by RadPageViewStripElement

The text alignment of DocumentTabs does not look good when the tabs are left aligned, the close button is visible and the text is vertically oriented (i.e. it looks horizontal when the tabs are aligned to the left). This would be best addressed if there is mechanism for rotating the Padding value of the Tabs when their alignment is different (left, top, etc.)

If you have a FloatingWindow with Name and Text set to "TestForm", save the layout and load it, you get a Dockplaceholder with default Name and Text "ToolWindow1". 

If you first dock the FloatingWindow, then float it again and finally save and load the layout, you get information both about the docked and floating windows in the xml.

RadDock tool tabs look incorrect with ControlDefault theme when RightToLeft layout is used.

Please run the attached sample project with the latest version. You will notice that the maximized floating window is not loaded properly. This used to work in versions prior to R1 2019.

Workaround: remove "WindowState=Maximized" from the XML.

To reproduce:
- Add RadDock with some document windows to a blank form.
- Make one widow floating and then remove the dock from the current form Controls collection on a button click.

In design-time the floating functionality from double click must be disabled.

This request concerns adding a state for the buttons in the ToolWindow caption, which will allow different theming for the buttons, when the window is active and inactive.

To reproduce: - add RadDock without document windows and five RadButtons with the following Click event handlers: private void radButton1_Click(object sender, EventArgs e) { this.radDock1.LoadFromXml(@"..\\..\\..\\layout1.xml"); } private void radButton2_Click(object sender, EventArgs e) { this.radDock1.LoadFromXml(@"..\\..\\..\\layout2.xml"); } //"Add" button private void radButton3_Click(object sender, EventArgs e) { this.documentContainer1.DockManager.AddDocument(new DocumentWindow(DateTime.Now.TimeOfDay.ToString())); } //Save layout 1 private void radButton4_Click(object sender, EventArgs e) { //add four document windows and save the layout 1 this.radDock1.SaveToXml(@"..\\..\\..\\layout1.xml"); } //Save layout 2 private void radButton5_Click(object sender, EventArgs e) { //add three document windows and save the layout 2 this.radDock1.SaveToXml(@"..\\..\\..\\layout2.xml"); } 
First add four document windows (via "Add" button click) and save layout 1 (via "Save layout 1" button click) on the RadDock and it creates 4 new Documents and save them in the xml. 
Restart the application and add three document windows (via "Add" button click) and save layout 2 (via "Save layout 2" button click). Load layout 1 (four document windows), then load layout 2. 
Everything is OK. But now load again layout 1. As a result ObjectDisposedException is thrown.

Workaround: before loading the xml, remove all document windows: radDock1.RemoveAllDocumentWindows(); radDock1.LoadFromXml(@"..\\..\\..\\layout1.xml");

To reproduce:

Add a RadDock and two ToolWindows. Drag the tool windows out and leave on on top of the RadDock, drag the other over the first tool window and you will notice drag hints from both - the RadDock and the ToolWindow

To reproduce:

Add a ToolWindow to RadDock. AutoHide it:

toolWindow1.AutoHide();

Then Hide it:

toolWindow1.Hide();

And show it:

toolWindow1.Show();

You will see that the window is docked but is not AutoHide

Workaround:

Call the AutoHide method instead of the Show method:

toolWindow1.AutoHide();