Button in WindowCommands doesn't get automatically bound by Caliburn.Micro

[mahapps]

Button in WindowCommands doesn't get automatically bound by Caliburn.Micro

I have no idea how to fix this, nor even where to start.

[becdetat]

Bugger :-D I had hoped I was just doing something stupid. The above is a usable workaround, is there any documentation it can be added to?

I'll see if I can debug this further.

If you checkout the gh-pages branch, thats where I'm keeping all the documentation. That ends up being generated at http://mahapps.com/MahApps.Metro

Happy to accept PR's for documentation :D

[becdetat]

So, my understanding is MetroWindow.WindowCommands are shown as part of the window's template (a ControlTemplate, Generic.xaml:557). But Caliburn only traverses the window's content ((current as ContentControl).Content - caliburn.micro's BindingScope.cs:93) which means it misses the WindowCommands.

This is stretching my WPF knowledge to where I'm only guessing but there's got to be some way Caliburn can bind to control templates. I'll start googling.

[becdetat]

It appears that Caliburn.Micro will only automatically traverse the visual tree and a few other places (see [here][http://caliburnmicro.codeplex.com/wikipage?title=All%20About%20Conventions] and search for 'visual tree') so this isn't a bug with MahApps.Metro, just a difference in implementation. So the tricky way around this would be to have a separate MahApps.Metro.Caliburn assm that provides a customised BindingScope.GetNamedElements which includes the headers, which probably isn't worth messing around with as the simplest workaround is a two-liner. This could just be documented somewhere:

Add the cal namespace to the root element:

xmlns:cal="http://www.caliburnproject.org"

Then attach the action to the element:

Controls:MetroWindow.WindowCommands>
    <Controls:WindowCommands>
        <Button x:Name="SayWat" Content="wat" cal:Message.Attach="SayWat"/>         
    </Controls:WindowCommands>
</Controls:MetroWindow.WindowCommands>

[becdetat]

oh, sweet.

[becdetat]

Closing this as it is a known upstream issue