Setting Dark mode from Settings Page makes the Minimize, Maximize, and Close buttons invisible.

[Omenrevlis]

Describe the bug

In Navigation Template I added the settings. By default, it implements the ability to switch the app to Dark, Light, or Default. When I change it to Dark the Mininimize, Maximize, and Close buttons are still set to forground black and are invisible unless you hover over them.

I have not modified the toolbar from what the template created.
I have not messed with setting any colors of anything. This is how it is after the template studio created it.

To Reproduce

1. Create a Navigation based Template project
2. Add a Settings page
3. Make sure your computer is set to light mode
4. Run the application
5. Go to the settings page
6. Change to Dark Mode (application only)

Additional context

I see where the TitleBarHelper and the ShellPage CS sets the forcolor. Interestingly, if I put a breakpoint in either and run debug to the breakpoint, then just continue running, the title bar foreground is correct.

So something is changing it back to light foreground settings, likely on another thread, but I'm not sure where.

When the main window is deactivated, you can see greyish buttons. But when the windows is active, they are the same color as the title bar (black) and cannot be seen.

Applies to the following platforms:

• WinUI
• WPF
• UWP

About your setup

• Visual Studio Version: Version 17.8.0 Preview 7.0
• Template Studio Wizard Version: v5.4
• Windows Build: Windows 11 Pro - 10.0.22621

[Mysterious-Dev]

If you use Windows App SDK 1.4, it's fixed with 52d63a4. We just need to wait @pratikone for a release binary ^^.

[Jay-o-Way]

Looks like microsoft/microsoft-ui-xaml#8899
@Mysterious-Dev where did you find the pr in MS repo that fixed it and for which exact version? I don't see any pr linkt to this ↑ issue.

[Jay-o-Way]

if you to need the custom title bar in 1.4, you can move away from Window.ExtendsContentIntoTitleBar and use the new APIs under Window.AppWindow.TitleBar

microsoft/microsoft-ui-xaml#8899 (comment)

What does the template do?

[Mysterious-Dev]

Looks like microsoft/microsoft-ui-xaml#8899
@Mysterious-Dev where did you find the pr in MS repo that fixed it and for which exact version? I don't see any pr linkt to this ↑ issue.

It's a PR for TemplateStudio. I think he used TemplateStudio 5.4 and updated WindowsAppSDK to 1.4 (with new TitleBar customisation).

[Jay-o-Way]

I know. I asked what your source was. And what method does the template use.

[Omenrevlis]

I am using TemplateStudio 5.4 and WindowsAppSKD 1.4

[pratikone]

New release of Template Studio is here. Do check if it is still happening.

[JoySurfer]

New release of Template Studio is here. Do check if it is still happening.

It seems that these function calls in TitleBarHelper are no longer necessary.

//var hwnd = WinRT.Interop.WindowNative.GetWindowHandle(App.MainWindow);
//if (hwnd == GetActiveWindow())
//{
// SendMessage(hwnd, WMACTIVATE, WAINACTIVE, IntPtr.Zero);
// SendMessage(hwnd, WMACTIVATE, WAACTIVE, IntPtr.Zero);
//}
//else
//{
// SendMessage(hwnd, WMACTIVATE, WAACTIVE, IntPtr.Zero);
// SendMessage(hwnd, WMACTIVATE, WAINACTIVE, IntPtr.Zero);
//}

[Omenrevlis]

New release of Template Studio is here. Do check if it is still happening.

I updated to Template Studio 5.5 on the existing solution. There is some improvement but not fully fixed.

If Windows is set to Dark Mode and App is set to default, it works.
If Windows is set to Dark Mode and App is set to Dark Mode, it works.
If Windows is set to Light Mode and App is set to Dark Mode, it does not work. They are hidden when window is Active. But visible when the window is inactive.

[Omenrevlis]

Starting a new Template Studio project to test and Good news, it works! So a new solution path is fine, but an upgrade to the Extension for Template Studio does not fix it. I can port all my stuff over to a new project. That's fine for me.

I started a template from scratch and when I changed to target .net 8 I had to add these to the project file xml for it to compile.

<ItemGroup>
  <RuntimeHostConfigurationOption Include="System.Runtime.Loader.UseRidGraph" Value="true" />
</ItemGroup>
<PropertyGroup>
  <UseRidGraph>true</UseRidGraph>
</PropertyGroup>

[Omenrevlis]

Well, I'm sorry but there is still some weirdness. Not with the pages themselves, but with ContentDialog. It tires to follow the OS for dark mode.

If OS is light mode, and app is set to default all is great.
If OS is dark mode, and app is set to default all is great.
if OS is dark mode, and app is dark mode all is great.
if OS is dark mode, and app is on light mode, the dialog is in dark mode.
If OS is in light mode and app is in dark mode. the dialog is in light mode

[Omenrevlis]

Just for reference, the content of the dialog box is a Page object.

[Omenrevlis]

There is also a measly bug I think no one would care too much about. If the app is set to default and you have a dialog on screen from your app when the OS is changed to a dark or light mode, it only applies to the dialog and not the main window. This fixes itself when you close and restart the app, but it feels odd when it is happening.

[pratikone]

@Omenrevlis no bug is small. Do open an issue for that.
Closing this one as it has been fixed.