Approved
Last Updated: 03 Jan 2017 21:13 by ADMIN
When loading a previously saved layout that includes a floated RadPane located on a currently not available monitor, that RadPane should be made visible on the available monitor.

Currently its is directly loaded in its saved location which is not visible.
Approved
Last Updated: 04 Jan 2017 07:14 by ADMIN
When the control contains RadPane instances which Content is provided by a MAF framework that content experiences flickers and disappearing when the RadPane is being floated, docked, pinned or unpinned.
Declined
Last Updated: 02 Dec 2015 15:48 by Tobias
ADMIN
Created by: Nasko
Comments: 4
Category: Docking
Type: Bug Report
1

			
Completed
Last Updated: 30 May 2016 12:08 by ADMIN
Available in LIB version 2016.2.530, it will be also available in the 2016 R2 SP1.
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: 16 Aug 2016 06:20 by ADMIN
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.
Won't Fix
Last Updated: 17 May 2016 14:02 by ADMIN
Approved
Last Updated: 04 Jan 2017 07:33 by ADMIN
By design in the current version of RadDocking when a hidden RadPane instance in a RadPaneGroup is made visible by changing the IsHiddden property of that pane to False, that RadPane is set to be SelectedItem in the group.


Make it possible to disable this functionality. This way the old selected RadPane in that RadPaneGroup will be persisted.
Approved
Last Updated: 03 Jan 2017 20:53 by ADMIN
Pinning a pane instance will cause that instance's tab to go to the first place of the group in which it is in the DocumetnHost of the control. This behavior could be observed in MS Visual Studio 2013
Completed
Last Updated: 17 Oct 2016 15:01 by ADMIN
Loading a layout containing a single empty RadPaneGroup inside the DocumentHost causes the IsInDocumentHost property of the group to return false.

Available in LIB version 2016.3.1017, it will be also available in the 2016 R3 SP1 release. 
Completed
Last Updated: 25 Oct 2016 13:57 by ADMIN
When used in second Tab in TabControl for example.

Available with the R3 2016 SP1 release. 
Approved
Last Updated: 03 Jan 2017 20:54 by ADMIN
Resizing a RadPane's splitter while its Header's or Content's ContextMenu is opened leads to incorrect resize
Completed
Last Updated: 03 Apr 2015 08:33 by ADMIN
Completed
Last Updated: 17 Oct 2016 14:59 by ADMIN
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. 
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.
Declined
Last Updated: 18 Feb 2015 08:29 by ADMIN
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.
Approved
Last Updated: 15 Mar 2019 17:39 by ADMIN
Currently when ScaleTransform is used ether on the RadDocking control or its container the compasses/drop cues which are shown when docking a RadPane instance have incorrect scaling and are placed incorrectly.

By design the control's scaling is determined by the scaling of the OS environment.