This happens when primary monitor is with lower resolution. Maximize the pane on the primary monitor, then maximize it to the second monitor - the maximized state is incorrect.

It would be great to be able to use other Resources other that the App.xaml for the Styles applied to the ToolWindow instances.

As they are automatically created and as expected are in a different visual tree accessing for example the Resources of the MainWindow is not possible.

Available in the 2016 Q1 SP1 Release.

When all of the RadDocument panes in the DocumentHost are closed the last one stays alive in .Net Framework 4.0. The issues can't be reproduced on machines with .Net Framework 4.5 installed

When the DragDropMode property is set to Deferred in partial trusted applications a security excpetion is being thrown.

- Binding Ishidden property of each pane to a menu section
- Save/Load the Docking layout on closing and opening the application
- Adding documents to module section using MVVM (DocumentHost)
- Persiste the state of each RadPane's content using PersistenceFramework.

Using the LayoutChangeEnded event to save the layout when docking a floating Pane causes that Pane to not be saved correctly.

After certain expand/collapse of RadExpander that is placed inside a floating RadPane the DataContext of the RadExpander is lost

This also causes the initial DataContext to be left out in the memory.
Available in LIB version 2015.3.1214, it will be also available in the 2016 Q1 Release.

Calling the LogicalTreeHelper.GetChildren() does not include the DocumentHost and its contents.
Available in LIB version 2015.3.1214, it will be also available in the 2016 Q1 Release.

In the following scenario:

    Floating Pane's size has been changed.
    The layout has been saved.
    The layout has been loaded.
    The Pane has been docked.
    Making the Pane floating should retain the custom size from point 1.

Available in LIB version 2015.2.817, it will be also available in the 2015 Q3 Release.

Create content control and change the content in it -when the content contains RadDock the WPF window lose focus.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

Showing a ContextMenu inside the AutoHideArea causes it to be closed immediately.
If a TextBox inside the AutoHideArea is right clicked the AutoHideArea is closed.

If you have more than one monitors and on one of them you maximize a ToolWindow, than dock another pane and undock it, the second pane's width will be equal to the width of the two monitors. 

The PaneHeader is shown and then immediately collapsed. 

Setting the PaneHeader to null can be used as a workaround if the project uses the default theme.