Workaround - set AutoScroll = false to Form that is being shows as MDI child 

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

OS language is zh-TW (Taiwan)

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.

To reproduce:

Add a RadDock with RightToLeft - Yes and add a few document windows. You will see that the Tabs will be rendered LeftToRight. The insertion behavior is correct.

RadDock - implement BackgroundImage property.

To reproduce:
- Add 2 RadFoms to a raddock in mdi mode.
- Dock the windows by using the left or right docking guide in the center.
- You will notice that the behavior is the same as like using the left or right side guides.

The main form inherit from the RadForm.

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

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.

This is a follow on from the forum entry http://www.telerik.com/community/forums/winforms/dock/toolwindow-theme-error.aspx 

This is not the exact issue I am having but should hopefully lead you in the correct direction. A panels visibility seems to vary depending on where it is.

If you run the program and open a new tool window by clicking the + button you will get a new docked window.
Change this to a tabbed document.
Then add another window and set it to be docked.
Then add another window and also set it to be docked. Then set it to autohide.

You will see on the tabbed document and the docked unautohide window that there are 2 lines of text. If you now let the auto toolwindow open you will see that there are now three lines of text in this window. The docked autohide is letting the text shine through but only when it is in this state.

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.

To reproduce:

Create MDI form using RadDock by following the article: http://www.telerik.com/help/winforms/dock-mdi-mode-automatic-mdi-form-handling.html You will notice that the Closing and Closed events of the MdiForms will not be invoked.

Workaround:

Subscribe to the FormClosing event of the main Form and close all the windows manually:

void Form1_FormClosing(object sender, FormClosingEventArgs e)
{
    this.RadDock.CloseAllWindows();
}

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)

Steps to reproduce: 
1. Add a RadDock to a form 
2. Add a document window
3. Add a button to the form and upon click add a user control to the document with Dock set to FIll 
4. Run the project and click the button. 
5. You will notice that the user control will not fill the parent container properly.

If there is a RadDock in UserControl and second UserControl, which inherits the first one, then the RadDock€™s layout in the second UC is damaged in design and run-time.