You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CanFloat property is set to False in my LayoutAnchorable control . The problem here is if the user try to drag the LayoutAnchorable (which is disabled using property) ,the LayoutAnchorable is getting removed from the pane and not visible anywhere. Is there any quick fix for issue?
<xcad:DockingManager SnapsToDevicePixels="True"
AllowMixedOrientation="True"
ShowSystemMenu="True"
VerticalAlignment="Stretch"
HorizontalAlignment="Stretch"
Margin="0 4 0 0 ">
<xcad:LayoutRoot>
<xcad:LayoutPanel Orientation="Horizontal">
<xcad:LayoutDocumentPane ShowHeader="False">
<xcad:LayoutDocument Title="Indicators">
<TextBlock Text="123" />
</xcad:LayoutDocument>
</xcad:LayoutDocumentPane>
</xcad:LayoutPanel>
<xcad:LayoutRoot.RightSide>
<xcad:LayoutAnchorSide>
<xcad:LayoutAnchorGroup >
<xcad:LayoutAnchorable Title="Messages"
AutoHideWidth="300"
CanClose="False"
CanFloat="False"
CanHide="False">
<TextBlock Text="123" />
</xcad:LayoutAnchorable>
</xcad:LayoutAnchorGroup>
</xcad:LayoutAnchorSide>
</xcad:LayoutRoot.LeftSide>
</xcad:LayoutRoot>
</xcad:DockingManager>`
```
This issue exists in version 3.5 and 3.6 . It was working finr in version 3.3
The text was updated successfully, but these errors were encountered:
Hi,
You are right. Thank you for reporting this. It will be fixed in v3.9.
In the meantime, you can go in file Xceed.Wpf.AvalonDock/DockingManager.cs,
in method StartDraggingFloatingWindowForContent,
and add the following check at the beginning of the method: if( ( contentModel == null) || !contentModel.CanFloat ) return;
CanFloat property is set to False in my LayoutAnchorable control . The problem here is if the user try to drag the LayoutAnchorable (which is disabled using property) ,the LayoutAnchorable is getting removed from the pane and not visible anywhere. Is there any quick fix for issue?
The text was updated successfully, but these errors were encountered: