Currently, the RadDock control exposes 2 methods: RemoveAllWindows() and RemoveAllDocumentWindows(). The first one removes all windows, while the second one removes all document windows. We can expose a similar method that removes all windows, except document windows.

Currently, loading the store layout in RadDock may result in different UI panels according to the available internal splitcontainers/panels that are invisible. Perhaps a "SaveAsDefaultLayout()" and "RestoreDefaultLayout()" method could be introduced. Thus, it wouldn't be necessary to clear the windows before loading XML layout.

Currently, when you load a layout and the XML contains a lot of windows, even though they may not all be visible, I have to set the Visible property to false on the RadDock control to eliminate some funky refreshes are visible to the user (something we want to avoid). I also wanted to mention that using SuspendLayout/ResumeLayout instead of using Visible=false/true does not work.  Maybe this is something the development team can investigate at some point as well.

Use cases:

1. You have a MainDocumentContainer with Document windows in it, placed in one under the other. Setting the DockState of the bottom DocumentWindow to Hidden, and restoring it afterwards, should place the DocumentWindow at the same place, instead of merging it with the above one

2. Same layout as above, when the layout is saved and then restored, the DocumentWindow positions should be exactly as they were

Currently tool windows cannot be re-sized proportionally in this scenario.

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

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.

http://blogs.msdn.com/b/zainnab/archive/2012/06/19/visual-studio-2012-new-features-preview-tab.aspx

support of Pin tab operation in DocumentContainer of RadDock

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.

The user should be allowed to modify the default behavior of floating windows and decide whether they should be owned by the main Form or they should act like normal Forms - with Minimize/Maximize options and appearing in the System's Taskbar.

This feature request refers to introducing a new ToolWindow property which will allow setting individually text to the ToolWindow's Caption and Tab.

using the RadDock component in a product that must support multiple montors.  I see some mention of this in the support forums, but I would like to confirm with you that RadDock does support docking on multiple monitors with dragging of panes/panels between monitors and full serialization of the layout on multiple displays. Add support to move and maximize DocumentWindow and ToolWindow in multimonitor system.

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.

RadDock - implement BackgroundImage property.

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

IMPROVE. RadDock - add possibility for replacing the page items in the DocumentWindows with custom ones.

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

One possible scenario is adding an application menu button like in RadRibbonBar.

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.