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: 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: 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}
Completed
Last Updated: 03 Jun 2019 06:26 by ADMIN
Release LIB 2019.2.603 (06/03/2019)
When the IsHidden property of a RadPane within a ToolWindow is set to True and then to false in quick succession, the ToolWindow is not shown. 

As a workaround, you can disable the animation of the ToolWindow:
<Style TargetType="telerik:ToolWindow">
<Setter Property="telerik:AnimationManager.IsAnimationEnabled" Value="False" />
</Style>

The above style need to be placed in the resources of the App.xaml in order to take effect on the ToolWindows, since they are displayed in a separated visual tree.
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: 07 May 2019 10:20 by ADMIN
Possible work-around of this problem:

private void RadDocking_ElementLoaded ( object sender, LayoutSerializationEventArgs e )
 {
     if ( e.AffectedElement is RadPaneGroup )
     {
         var PaneGroup = e.AffectedElement as RadPaneGroup;
         var Panes = PaneGroup.EnumeratePanes().ToList();
         var SelectedIndex = PaneGroup.SelectedIndex;

         for ( int Index = 0; Index < Panes.Count; Index++ )
         {
             if ( ( Panes[ Index ].IsHidden || !Panes[ Index ].IsPinned ) && Index <= SelectedIndex )
             {
                 SelectedIndex++;
             }
         }

         PaneGroup.SelectedIndex = SelectedIndex;
     }
 }
Completed
Last Updated: 19 Apr 2019 14:05 by ADMIN
Release LIB 2019.1.422 (04/22/2019)
The exception is reproduced when multiple toolwindows with nested owners are floated and they are reloaded by re-merging the dictionaries in App.xaml in a NoXaml scenario.
Completed
Last Updated: 19 Apr 2019 12:58 by ADMIN
Release LIB 2019.1.422 (04/22/2019)

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.

Completed
Last Updated: 16 Apr 2019 08:16 by ADMIN
Release LIB 2019.1.422 (04/22/2019)
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.
Declined
Last Updated: 22 Mar 2019 12:48 by ADMIN
Created by: Marco
Comments: 2
Category: Docking
Type: Feature Request
1

Having Problems with unreadable Tabs in RadPaneGroup: TabsSqueeze.png

I think I found a Solution with OverflowMode and ScrollViewer:

<telerik:RadPaneGroup x:Name="DocumentGroup" ScrollViewer.HorizontalScrollBarVisibility="Auto" OverflowMode="Scroll">

Problem:

After Loading Layout the OverflowMode is not respected anymore.

I found this ticket in Silverlight, what discribes the Problem and is approved: Docking: I would like OverflowMode to work for all RadPaneGroup in xaml/codebehind and this be persisted through SaveLayout/LoadLayout

And i found this documentation, which say, using OverflowMode can lead to unexpected behaviors:
https://docs.telerik.com/devtools/wpf/controls/raddocking/general-information/not-supported-properties

so i report this as a feature instead of a bug.

Please sea atteched an example project: TabWrapProblem.zip
Usage: Save and than Load the Layout -> Scrolling of tabs break

Approved
Last Updated: 21 Mar 2019 13:19 by ADMIN
Approved
Last Updated: 15 Mar 2019 17:39 by ADMIN
Approved
Last Updated: 15 Mar 2019 17:39 by ADMIN
Approved
Last Updated: 15 Mar 2019 17:39 by ADMIN
Just like in Visual Studio, a floating pane, which I want to dock (for example to the bottom), can either take the whole width or just the width that is left.

For example:
At start, the panes in the bottom does not consume the whole window width. After undocking the panes and docking them back, the compass only shows me an option to dock the panes while consuming the whole width.

I have no option to return to the original state (like in Start.png). The only way to return to that state is undock and re-dock the right pane, and then dock and re-dock the left pane.

Visual Studio has this feature (see image).
Approved
Last Updated: 15 Mar 2019 17:39 by ADMIN
Provide an easy functionality to exclude a pane or group of panes from reordering when AllowDragReorder is set to True.
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.
Approved
Last Updated: 15 Mar 2019 17:39 by ADMIN
Approved
Last Updated: 15 Mar 2019 17:39 by ADMIN
Expose information about the used Compass when docking a Pane.
1 2 3 4 5 6