Approved
Last Updated: 18 Sep 2019 12:50 by ADMIN
The CustomElementLoading event can't be canceled without creating a new instance of the custom element.

As a workaround in the CustomElementLoading event handler you can call the SetAffectedElement() with creating DependencyObject and then Cancel the event by setting the Cancel property.
private void RadDockingOnCustomElementLoading(object sender, LayoutSerializationCustomLoadingEventArgs e)
{
    if (e.CustomElementTypeName == "MyRadPane")
    {
        e.SetAffectedElement(new DependencyObject());
        e.Cancel = true;              
    }
}
Approved
Last Updated: 07 Jun 2019 10:52 by ADMIN

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}
Approved
Last Updated: 29 May 2019 13:50 by ADMIN

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

Approved
Last Updated: 09 Apr 2019 07:07 by ADMIN
This issue is replicable in a setup which has two monitors and wit different DPI.
If a docking window is resized to a width over both monitors, when the window is more than a half on the monitor with lower DPI, it is not possible to dock it.
Approved
Last Updated: 21 Mar 2019 13:19 by ADMIN
Approved
Last Updated: 07 Feb 2019 15:40 by ADMIN
Created by: Martin Ivanov
Comments: 0
Category: Docking
Type: Bug Report
1
A memory leak related to the automation peers of the RadPane and RadPaneGroup appears when you close a pane (using its Close button) even if you call its RemoveFromParent() method.

To work this around disable the automation peers. To do so please set the static AutomationManager.AutomationMode property toAutomationMode.Disabled.
public MainWindow()
{
    AutomationManager.AutomationMode = AutomationMode.Disabled;
    InitializeComponent();
}

The issue originates from ItemsControlAutomationPeer. It is reported to Microsoft in their old connect portal here =>

https://connect.microsoft.com/VisualStudio/feedback/details/838165/memory-leak-in-the-itemscontrolautomationpeer-because-items-removed-from-the-itemscollection-are-still-strongly-held-by-the-weakrefelementproxystorage
Approved
Last Updated: 28 Dec 2018 08:39 by ADMIN
The RadDocking control template hosts several AutoHideArea elements, one for each auto-hide placement - left, top, right, bottom. When you unpin a RadPane, it goes into one of those areas. The active auto-hide area where the pane will go is determined by the State of the topmost RadSplitContainer.

Allow manually setting the auto-hide area where the RadPane will go when unpinned.
Approved
Last Updated: 21 Nov 2018 16:55 by ADMIN
The RadPaneGroup inherits RadTabControl and the TabStripPlacement property. Currently the RadPaneGroup does not support setting this property as the corresponding ControlTemplates are not implemented.
Approved
Last Updated: 18 Sep 2018 09:38 by ADMIN
A possible workaround has been demonstrated in the attached project.
Approved
Last Updated: 29 Jul 2019 09:42 by ADMIN
The compass elements are not on the proper places when the docking is on the second monitor. To reproduce this the DPI of the monitors should be different for example 125% (main) and 150% (secondary). Also, to reproduce this you will need to enable the DPI awareness of the application by setting the dpiAware and dpiAwareness settings in the app.manifest file.
Approved
Last Updated: 19 Apr 2018 10:15 by Vladimir
Approved
Last Updated: 22 Mar 2018 13:05 by ADMIN
Approved
Last Updated: 15 Mar 2019 17:39 by ADMIN
Approved
Last Updated: 10 Nov 2017 18:04 by ADMIN
Approved
Last Updated: 30 Oct 2017 15:02 by ADMIN
Approved
Last Updated: 03 Jan 2017 21:16 by ADMIN
ADMIN
Created by: Georgi
Comments: 0
Category: Docking
Type: Feature Request
0

			
Approved
Last Updated: 03 Jan 2017 21:09 by ADMIN
ADMIN
Created by: Georgi
Comments: 0
Category: Docking
Type: Feature Request
0
    After starting the application, there are 2+ RadPane instances
    Each RadPane contains multiple TextBox controls
    Click on a TextBox in first RadPane
    Switch to the next RadPane
    go back to the first RadPane

The desired behavior is that the focus is restored to the focused element in step 3. Currently no element is focused. The same scenario in RadTabControl is a bit different and the TabControl focused the first element in its TabItem content.
Approved
Last Updated: 25 Aug 2016 12:58 by ADMIN
ADMIN
Created by: Geri
Comments: 0
Category: Docking
Type: Bug Report
0
Possible workaround:

A custom RadDocking control can be created, in which the OnCreateAutomationPeer() method is overridden. OnCreateAutomationPeer() should return a custom RadDocking AutomationPeer, in which the ToolWindowAutomationPeer is removed from the collection of child elements of RadDocking AutomationPeer.
Approach demonstrated in the attached project.
1 2 3 4 5