Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Flyout problem with ActualWidth #2656

Closed
osnoser1 opened this issue Sep 17, 2016 · 1 comment
Closed

Flyout problem with ActualWidth #2656

osnoser1 opened this issue Sep 17, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@osnoser1
Copy link

What steps will reproduce this issue?

Window maximixe and open flyout

Expected outcome

Correct width

Environment

  • MahApps.Metro v1.2.4, v1.3.0-ALPHA189
  • Windows 7, 10
  • Visual Studio 2015
  • .NET Framework 4.5.1

Image

captura de pantalla 2016-09-17 11 48 23

@punker76 punker76 added the Bug label Sep 19, 2016
@punker76 punker76 self-assigned this Sep 19, 2016
@punker76 punker76 added this to the 1.3.0 milestone Sep 19, 2016
punker76 added a commit that referenced this issue Sep 19, 2016
  It's not goot to bind to ActualWidth of a Window, cause it gives us wrong values, it's maybe a WPF bug. So it's better to use the FlyoutsControl property.
@punker76
Copy link
Member

@osnoser1 I've updated the demo for this, cause we should use the FlyoutsControl for the binding. The ActualWidth of the Window gives us a wrong value if it's maximized, maybe another WPF bug...

<Controls:Flyout x:Name="settingsFlyout"
                 Controls:ControlsHelper.ContentCharacterCasing="Upper"
                 Width="{Binding RelativeSource={RelativeSource FindAncestor, AncestorType=Controls:FlyoutsControl}, Path=ActualWidth}"
                 Margin="200 0 0 0"
                 AreAnimationsEnabled="False"
                 Header="Settings"
                 Position="Right">
</Controls:Flyout>

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Development

No branches or pull requests

2 participants