Got this weird behavior with RadDocking with multiple monitors.

http://www.youtube.com/watch?v=8DDX5OiYRyM

As you could see the pane is being opened on the wrong side.

This happens only when the application is fully maximized, if its resized then this problem does not occur.

I am not able to reproduce this with a simple example. But you could contact me I can help in investigation.

workaround:
add the following visual state to the DocumentHostTemplate of the RadPaneGroup:

<VisualStateManager.VisualStateGroups>
    <VisualStateGroup x:Name="DropDownDisplayStates">
        <VisualState x:Name="DropDownButtonCollapsed" />
        <VisualState x:Name="DropDownButtonVisible">
            <Storyboard>
                <ObjectAnimationUsingKeyFrames Storyboard.TargetName="DropDownButtonElement" Storyboard.TargetProperty="Visibility">
                    <DiscreteObjectKeyFrame KeyTime="0">
                        <DiscreteObjectKeyFrame.Value>
                            <Visibility>Visible</Visibility>
                        </DiscreteObjectKeyFrame.Value>
                    </DiscreteObjectKeyFrame>
                </ObjectAnimationUsingKeyFrames>
            </Storyboard>
        </VisualState>
    </VisualStateGroup>
</VisualStateManager.VisualStateGroups>

and remove the trigger targeting the drop down button.

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.

Panes that are autohidden are cut if resized too much - this is due to limitation in WPF that popups should not cover more than 75% of the screen.

Removing item from the PanesSource collection causes NullReferenceException

When Saving and Loading a layout which has empty DocumentHost an ArgumentOutOfRangeException is thrown

The fix will be available in the R1 2018 SP2 Release.

In nested RadDocking scenarios if the inner RadPane's content contains a ScrollViewer pressing "Tab" or "Tab + Shift" (keyboard navigation) the focus is moved out of the RadPane's content into the parts of the RadDocking.

When the content of a RadPane contains an ScrollViewer it is scrolled to its end when the RadDocking control is used in nested docking scenarios.

Available with the 2015 Q3 release.

Regions in panes content are not resolved when the pane is unpinned and collapsed. This happens only when you change the regions in runtime while the pane is unpinned and collapsed.

When used in second Tab in TabControl for example.

Available with the R3 2016 SP1 release. 

Dynamically adding RadPane to PaneGroup, the header of the pane does not appear on the second added pane.

To workaround this the OnApplyTemplate() method can be called after the RadPane is added to the RadPaneGroup.

This happens because in the current version of Telerik, the IsTopmost of the ToolWindow that host the floating pane is set to True. That was needed for a related new functionality, but it brings a major behavioral change in the RadDocking control.

To work this around, you can subscribe to the ToolWindowCreated event of RadDocking and set the IsTopmost property of the creating ToolWindow to False.

private void RadDocking_ToolWindowCreated(object sender, Telerik.Windows.Controls.Docking.ElementCreatedEventArgs e)
{
    var window = (ToolWindow)e.CreatedElement;
    window.IsTopmost = false;
}

When move the most left pane in a split container above some other pane in the same split container the second splitter is created.

Available in LIB version 2016.3.1017, it will be also available in the 2016 R3 SP1 release. 

RadPane setting CanFloat, CanUserPin & CanUserClose to false, ContextMenuTemplate="{x:Null}" and PaneHeaderVisibility="Collapsed" still leaves a small part of the header visible and clickable. If there is any work-around can you please let me know. Version 2014.3.1202.45, using Framework 4.5 with VS2013.

Hello Support,

we are using the RadDocking.LayoutChangeEnded event to store the docking layout (via RadDocking.SaveLayout) after the user has changed it.

When animations are enabled (default) everything works as expected and all groups, split containers, and panes are included when in the XML written by RadDocking.SaveLayout.

However, when disabling animations (either using AnimationManager.IsGlobalAnimationEnabled or custom styles for RadWindow and/or ToolWindow setting AnimationManager.IsAnimationEnabled to false) the RadDocking.LayoutChangeEnded event is raised too early.

The faulty behavior can be reproduced with the attached demo application as follows:

1. start the application (App.xaml includes a style for ToolWindow with animations disabled)

2. drag the pane "Solution Explorer" out of the application to create a new tool window

3. drag the "Solution Explorer" tool window onto the "Properties" pane's compass and drop it below "Properties", so that "Properties" and "Solution Explorer" are both pinned right in the application above each other

4. when inspecting the layout written to the "Output" pane you will find that the entry for the RadPane "Solution Explorer" is missing

Any additional change to the docking layout (like resizing a pane) will update the layout and show all panes again.

When enabling animations in the ToolWindow style the above steps will result in the complete layout being written to the "Output" pane.

Please let me know should you require further information for reproduction of this bug.

Best regards,

Oliver