Won't Fix
Last Updated: 20 Jan 2016 14:55 by ADMIN
Using the LayoutChangeEnded event to save the layout when docking a floating Pane causes that Pane to not be saved correctly.
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.
Declined
Last Updated: 01 Apr 2014 14:48 by ADMIN
Created by: Kiranjeet
Comments: 1
Category: Docking
Type: Feature Request
2
I have a scenario where I only want to unhide the pane when certain property of the document is true.

For example: I have 3 panes A,B and C

Panes A and C are visible.

Active Pane should always be Pane A.

By default pane (B) is hidden.

Now when I set the IsHidden Property of the pane B to FALSE. Pane B now becomes the active pane.

I still want Pane A to be the Active Pane, but show the Pane B in background.

If I try setting the Pane A to be the active pane after Pane B is shown. It flickers which you can see here http://screencast.com/t/dGvU7UwUyYp

Is there any way i can unhide the pane in background while the active pane remains the same without having this flickering scenario.
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: 17 Aug 2015 12:22 by Grzegorz
Available in LIB version 2015.2.817, it will be also available in the 2015 Q3 Release.
Completed
Last Updated: 03 Apr 2015 08:33 by ADMIN
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: 19 Feb 2016 07:52 by ADMIN
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.
Unplanned
Last Updated: 03 Jan 2017 21:12 by ADMIN
Currently when a Pane becomes floating and we are still holding it with the mouse the ToolWindow could not be snapped. First the mouse should be released and right after that the ToolWindow could be snapped.
Unplanned
Last Updated: 15 Mar 2019 17:39 by ADMIN
Completed
Last Updated: 02 Jan 2018 12:08 by ADMIN
Available in LIB version 2017.3.1225, it will be also available in the R1 2018 Release.
Unplanned
Last Updated: 15 Mar 2019 17:39 by ADMIN
Completed
Last Updated: 29 Oct 2020 08:03 by ADMIN
Release LIB 2020.3.1102 (11/02/2020)
A possible workaround has been demonstrated in the attached project.
Completed
Last Updated: 30 Oct 2019 07:49 by ADMIN
Release LIB 2019.3.1103
Completed
Last Updated: 02 Jun 2022 11:10 by ADMIN
Release LIB 2022.2.606 (06 June 2022)

Description:

When using a display with scaling setting to more than 100%, floating pane docking does not work as intended. When dragging a pane out of a PaneGroup, and without releasing it, you drop it on top of another tab (so it is inserted into that position in the PaneGroup), nothing happens (window stays floating in that position). If you drag the already floating window on top of the same tab, then the default behavior happens and the pane is docked into the group. This behavior is reproducible on the Telerik UI for WPF Demo app.

See attached video for reproduction case in Demo app.

 

Technical Details:

For the failing scenario DragDelta on the ToolWindow is being triggered with wrongly scaled mouse position. On second drag drop operation, DragDelta receives properly scaled mouse position.

Failure case mouse positions:

DRAG START {864,128.8}
DRAG DELTA {871.2,142.4}
...
DRAG DELTA {864.8,114.4}
DRAG END {1081,143}

Second case mouse positions:

DRAG START {862.4,116}
DRAG DELTA {873.6,160.8}
...
DRAG DELTA {860.8,112}
DRAG END {860.8,112}
Unplanned
Last Updated: 01 Nov 2019 09:21 by ADMIN

This feature request is related to Ticket 1435779

 

Image for context

 

Currently, there's no support for increasing the drag threshold for the items on the orange box. Even after setting the values below.

DragDropManager.MinimumHorizontalDragDistance = 5000;
DragDropManager.MinimumVerticalDragDistance = 5000;

 

It would also be beneficial if instead of just relying on the drag threshold which is the box. Add a support for a sort of "Drag Time" concept where we can define how long the user should've held the actual pane before dragging/going outside the threshold.

Completed
Last Updated: 03 Sep 2020 13:45 by ADMIN
Release LIB 2020.2.831 (08/31/2020)
The compass is misplaced on the second monitor when launching *.exe on monitors with higher DPI. The tool window also is not positioned correctly. 

  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitor</dpiAwareness>
      <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
    </windowsSettings>
  </application>
Unplanned
Last Updated: 09 Sep 2020 09:12 by ADMIN
A property can be exposed to control the Width/Height of the RadGridResizers between the different elements and their respective Margins.
Unplanned
Last Updated: 08 Dec 2020 11:54 by ADMIN

Hi,

 

In most docking applications (Telerik WinForms, Visual Studio), it is possible to right click on the pane-tab header and get the options:

- New Horizontal Tab Group

- New Vertical Tab Group

- Move to Next Tab Group 

etc.

 

This would nice in WPF as well

 

/Brian

 

 

Completed
Last Updated: 12 Jan 2022 14:33 by ADMIN
Release R1 2022
When several unpinned panes are saved, each one of them is duplicated inside the generated XML.