When changing the DragDropMode in runtime, the panes behave unexpectedly.

If changing from Immediate to Deferred:

* Docked panes are not movable (no compass and no deferred adorner is being shows)

* Floating panes that are being docked do have the compass and the deferred adorner, when you try to move them after they were docked. 

 

If you change is back from Deferred to Immediate:

* Panes that you could not move can be moved (and then become floating) again/

* The panes that did have  the compass and the deferred adorner, don't move when you try to drag them. However, when you release the mouse button, then the start moving with the mouse pointer... without any mouse button pressed.


I've debugged the controls using the source code, and I've concluded that.

RadPane.UdateAllowDrag() is being called on PaneLoaded, which happens when I drag a floating pane into the Docking area.

In this case, when the DragDropMode is set to Deferred, then AllowDrag is set to True (with the call of DragDropManager.SetAllowDrag)

This is why that pane does have the Deferred Drag Adorner (The Drag Cue), while other panes doesn't.

 

On the other hand, when I change the DragDropMode to be Immediate again, then that pane is left with AllowDrag set to true, and it is registered to the DragDropManager events, which causes the second problem.

 

In my opinion, the RadPane.UpdateAllowDrag() should be called also when the DragDropMode is changed.

The the keyboard focus is also lost if you undock a RadPane from its docked state.
As a workaround you can persist the focus as shown in the RestoreFocusOnStateChanged SDK example, that can be found here:
https://github.com/telerik/xaml-sdk/tree/master/Docking/RestoreFocusOnStateChanged

Hello Support,

I have some hidden panes (see attachement). The Problem is that when I try to reorder and save the layout and reload it, the panes are not ordered as wished.

I there a way to provide it?

Best regards,

Frédéric Le Blay.

In OS two monitors are configured: monitor 1 (3840x2160) scale: 200% and monitor 2 (1920x1200) scale 100%.

Our wpf application has a main window, maximized on screen 1 and a child window maximized on screen 2.

In the app.manifest we use per monitor dpi awareness:

<application xmlns="urn:schemas-microsoft-com:asm.v3">
  <windowsSettings>
    <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">True/PM</dpiAware>
    <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2,PerMonitor</dpiAwareness>
  </windowsSettings>
</application>

Both windows have a RadDocking instance with a docked RadPane like:

<Grid>
  <telerikDocking:RadDocking Name="Docking"                              
                             HasDocumentHost="True" 
                             telerik:DragDropGroup.Name="VDDragDropGroup">
    <telerikDocking:RadDocking.DocumentHost>
      
            ...
          
    </telerikDocking:RadDocking.DocumentHost>
    <telerik:RadSplitContainer InitialPosition="DockedBottom">
      <telerik:RadPaneGroup>
        <telerik:RadPane Header="Test Panel" IsDockable="True">
          <Border Background="Green">
            <TextBlock Text="Test Panel" HorizontalAlignment="Center" VerticalAlignment="Center"/>
          </Border>
        </telerik:RadPane>
      </telerik:RadPaneGroup>     
    </telerik:RadSplitContainer>
  </telerikDocking:RadDocking>
</Grid>

If you drag and move the docked panel from screen 2 to screen 1 the compass at screen 1 is only shown if the mouse position is in the first quadrant of screen 1 . The compass is shown on the correct place but cannot be activated, so that no dropping is possible.

Without unsing per monitor dpi awareness everything works fine. Unfortunately we must use per monitor dpi awareness for our application.

This bug is also reproducable in V2023.3.1218.

The fix will be available in the R1 2018 SP2 Release.