Completed
Last Updated: 30 May 2016 12:06 by ADMIN
With code below the radPane will remain hidden (radPane is floating pane):radPane.IsHidden = true;

radPane.IsHidden = false;

Available in LIB version 2016.2.530, it will be also available in the 2016 R2 SP1.
Completed
Last Updated: 26 May 2016 15:28 by ADMIN
Completed
Last Updated: 25 May 2016 08:20 by sho
Completed
Last Updated: 16 May 2016 10:57 by ADMIN
If DragDropMode is set to Deferred when trying to dock a Pane inside a compass that is over the dragged Pane, the dock operation is not completed correctly.

Available in LIB version 2016.2.516, it will be also available in the R2 2016 SP1 Release.
Completed
Last Updated: 16 May 2016 10:56 by ADMIN
When DragDropMode is set to Deferred and Pane are moved around in the Docking control if the layout is saved and loaded some Panes are rendered incorrectly.

Available in LIB version 2016.2.516, it will be also available in the R2 2016 SP1 Release.
Completed
Last Updated: 29 Apr 2016 11:58 by Markus Hopfenspirger
When Panes are placed above each other, after resizing their horizontal size, saving and loading the layout caused incorrect layout.
Completed
Last Updated: 28 Apr 2016 13:15 by ADMIN
In some scenarios the SplitterChange is not rounded number and this cause invalid layout load. 

Workaround: Edit the saved xml and round the value.
Completed
Last Updated: 18 Apr 2016 06:12 by ADMIN
When a Pane is floated and added to a specific position in a PaneGroup saving the layout saves its position as last Pane in the group
Completed
Last Updated: 11 Apr 2016 14:26 by Licensing
Available in LIB version 2016.1.411, it will be also available in the 2016 R2 release.
Completed
Last Updated: 21 Mar 2016 19:06 by ADMIN
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.
Completed
Last Updated: 10 Mar 2016 09:57 by Etienne
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.
Completed
Last Updated: 22 Jan 2016 13:26 by ADMIN
ADMIN
Created by: George
Comments: 0
Category: Docking
Type: Bug Report
2

			
Completed
Last Updated: 20 Jan 2016 15:31 by ADMIN
- 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.
Completed
Last Updated: 14 Dec 2015 15:05 by ADMIN
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.
Completed
Last Updated: 14 Dec 2015 15:04 by ADMIN
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.
Completed
Last Updated: 16 Jul 2015 07:54 by ADMIN
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.
Completed
Last Updated: 14 Jul 2015 06:13 by ADMIN
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. 
Completed
Last Updated: 11 May 2015 13:04 by ADMIN
The same issue is observed when a WindowsFormsHost is placed inside RadPane. In that scenario the "made floating" animation of the RadPane instances is suppressed by the WindowsForms integration leading to flickering issues.
Completed
Last Updated: 03 Apr 2015 08:33 by ADMIN
Completed
Last Updated: 03 Apr 2015 08:32 by ADMIN
Moving a ToolWindow when the DPI of the Window 7, 8 is higher then 100% causes incorrect offset to the mouse pointer to by applied. 

This issue leads to the following unexpected behaviors when ran under Window 8 OS:
When the:
- DragDropMode is set to Deferred. The compasses are not hidden after reorder.
- AllowDragReorder is set to True. In this scenario you should be able to reorder tabs without the need to float team. The incorrect offset causes them to be floated making it impossible to reorder tabs as expected.