As for your first question about why a function does nothing, I think this may be relevant to your project hierarchy. Using MUI is the main (and only) window for one of my applications
<mui:ModernWindow x:Class="namespace.MainWindow" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:mui="http://firstfloorsoftware.com/ModernUI" Title="Window Title" IsTitleVisible="True" ContentSource="/Pages/Home.xaml" Style="{StaticResource MyModernWindow}"> <mui:ModernWindow.TitleLinks> <mui:Link DisplayName="settings" Source="/Pages/SettingsPage.xaml" /> </mui:ModernWindow.TitleLinks>
in my project hierarchy, I have my project root (CSPROJ file), MainWindow.xaml, and then the Pages folder. In my pages folder I have SettingsPage.xaml. The source attribute in the mui: Link tag points to the real path of my main window to my settingsPage.xaml file. The MUI will then download and show this path in the content provider, which is placed in your main window for you according to the default style template for MUI ModernWindow. No additional code is required on your part for navigation (until you need complicated navigation by subspecies).
my settingsPage.xaml file is a regular user control with a grid having a style assigned to the style of the static resource ContentRoot, since it will also contain additional views / pages.
Mui source can be found on GitHub at Mui GithubLink . Here you can download a sample program, the code of which is in the same repository in the application Link here for convenience .
I am not familiar with Caliburn.Micro, therefore I am not sure how these two are combined together, for example, the requirements of Caliburn.Micro for work. I know how MUI integrates with MVVM backlighting, and in my research there are many examples of this found on the Internet.
xtreampb
source share