-
Notifications
You must be signed in to change notification settings - Fork 884
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AvalonDock #1119
Comments
BoucherS[CodePlex] |
BoucherS[CodePlex] When the LayoutAnchorables are grouped, auto-hiding the group should auto-hide all of its LayoutAnchorables. You can not, at the moment ,auto-hide only 1 LayoutAnchorable from a LayoutAnchorablePanegroup. Issue https://wpftoolkit.codeplex.com/workitem/22503 has been created to address this. |
maratmusaev[CodePlex] Thank you, |
BoucherS[CodePlex] Can you be more precise, based on your sample ? ―――― |
maratmusaev[CodePlex] I have a question though. Why when clicked on auto hide button the whole group gets auto hidden not just individual window? Is there any way to make just the target window to be auto hidden not the whole group? |
BoucherS[CodePlex] Can you go in file :
Tell me if it helps. |
maratmusaev[CodePlex] The layout that we want is LayoutXml2.xml file which is No Document option in the combo box. LayoutXml2 option does not have LayoutDocumentPaneGroup, which causes this issue of docking everything to the right. LayoutXml1 and LayoutXml3 work correctly when clicking auto hide - docks in a right position not everything to the right of main window. However, LayoutXml1 has a big gap between Window2/Window3 and Window4. If I could get right this gap than I would use this Let me if this is clear. |
maratmusaev[CodePlex]
|
BoucherS[CodePlex] Can you submit a sample of this please. ―――― |
Today I downloaded the March 5, 2018 v3.3.0 version of Toolkit. AvalonDock still contains a gap between the windows. I described the issue in the above message with sample solution that I provided last year (This blog was hosted on CodePlex site). I remember someone suggested a solution and worked, but I can't remember the solution he gave me. Here is the original question from above: "maratmusaev[CodePlex] |
Hi, Since Codeplex has closed, could you attached your sample on github (if not already resolved in latest version) |
It always "pins" to the right side, even if the anchor is added to LayourRoot.LeftSide via code-behind using a custom ILayoutUpdateStrategy. Here is a fix that worked great for me. Exensions.cs public static AnchorSide GetSide(this ILayoutElement element)
{
var parentContainer = element.Parent as ILayoutOrientableGroup;
if (parentContainer != null)
{
if (!parentContainer.ContainsChildOfType<LayoutDocumentPaneGroup, LayoutDocumentPane>())
return GetSide(parentContainer);
foreach (var childElement in parentContainer.Children)
{
if (childElement == element ||
childElement.Descendents().Contains(element))
return parentContainer.Orientation == System.Windows.Controls.Orientation.Horizontal ?
AnchorSide.Left : AnchorSide.Top;
var childElementAsContainer = childElement as ILayoutContainer;
if (childElementAsContainer != null &&
(childElementAsContainer.IsOfType<LayoutDocumentPane, LayoutDocumentPaneGroup>() ||
childElementAsContainer.ContainsChildOfType<LayoutDocumentPane, LayoutDocumentPaneGroup>()))
{
return parentContainer.Orientation == System.Windows.Controls.Orientation.Horizontal ?
AnchorSide.Right : AnchorSide.Bottom;
}
}
}
Debug.Fail("Unable to find the side for an element, possible layout problem!");
return AnchorSide.Right;
} Regards, |
It's doing the same thing with me as well. |
This issue of always hiding to the right side is causing us pain as well. |
Hi, Did you try with the latest version ? http://xceed.com/xceed-toolkit-plus-for-wpf/ Can you confirm that this is fixed in the latest v3.7 version ? |
No, since I cannot use the Plus Edition. |
You can try it for free for 45 days here : http://xceed.com/xceed-toolkit-plus-for-wpf/ |
maratmusaev[CodePlex]
Avalondock 3 autohide button always auto hides to the right. Can anyone help to resolve the issue?
The text was updated successfully, but these errors were encountered: