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.

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

When you add a few DocumentWindows to RadDock and you undock one of them to a floating window, then undock another one in the same floating window you will see two tabs. In the main area the selected tab is bolded, the functionality should be the same in the floating windows

For the time being use the following code to manually bold the tabs:

this.RadDock.FloatingWindowCreated += RadDock_FloatingWindowCreated;
...
void RadDock_FloatingWindowCreated(object sender, FloatingWindowEventArgs e)
{
    e.Window.Controls[0].ControlAdded += Form1_ControlAdded;
}

void Form1_ControlAdded(object sender, ControlEventArgs e)
{
    DocumentTabStrip tabStrip = e.Control as DocumentTabStrip;
    tabStrip.ControlAdded -= Form1_ControlAdded;
    if (tabStrip != null)
    {
        tabStrip.SelectedIndexChanged += tabStrip_SelectedIndexChanged;
    }
}

void tabStrip_SelectedIndexChanged(object sender, EventArgs e)
{
    DocumentTabStrip tabStrip = sender as DocumentTabStrip;
    if (tabStrip != null)
    {
        foreach (DocumentWindow item in tabStrip.Controls)
        {
            item.TabStripItem.ResetValue(RadItem.FontProperty, ValueResetFlags.Local);
        }

        tabStrip.SelectedTab.TabStripItem.Font = new Font(tabStrip.SelectedTab.Font.FontFamily, tabStrip.SelectedTab.Font.Size, FontStyle.Bold);
    }
}

Add the ability to programatically show AutoHidden window

Add the ability to easily turn on/off the DockingGuides

RadDock - implement BackgroundImage property.

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.

There should be mechanism for specifying which windows should be saved by the SaveToXml method.

Resolution: 
You need to subscribe to the DockWindowSerializing event to prevent saving of window. Please refer to the following code example: 
void radDock1_DockWindowSerializing(object sender, DockWindowCancelEventArgs e)
{
    if (e.NewWindow.Text == "WindowName")
    {
        e.Cancel = true;
    }
}

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.

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

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.

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

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.

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.

Currently it is not possible to customize the tool window animation and there is no animation when closing the tool window.

Resolution: 
Set the AutoHideAnimation and the AutoHideAnimationDuration properties of RadDock