You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running on Windows 10 or Windows 11, JPEGView has the "standard" Win32 look regardless of which theme is selected. This means title bars and context menus are both white even when Windows is using its dark theme.
I do realise that the ability to seamlessly switch between the white and dark themes is mostly a UWP feature, but maybe implementing it in JPEGView isn't difficult with XAML Islands.
Microsoft also has (mostly undocumented last I checked) APIs to accomplish the same thing on Win32 programs, as can be easily seen in explorer and powershell/cmd.
I think this change would make it look better on modern versions of Windows, even if it's entirely cosmetic.
The text was updated successfully, but these errors were encountered:
I am not sure how to do this at this time... but I'll label this a feature request for right now.
It sounds like something cool to do though, but yeah, the current way JPEGView is coded is that it's just generating the Win32 window objects... since the app was created long before this "Theme" world was created that we live in. I'm a big fan of dark mode myself... I'll look into it, but probably not a priority at the moment.
When running on Windows 10 or Windows 11, JPEGView has the "standard" Win32 look regardless of which theme is selected. This means title bars and context menus are both white even when Windows is using its dark theme.
I do realise that the ability to seamlessly switch between the white and dark themes is mostly a UWP feature, but maybe implementing it in JPEGView isn't difficult with XAML Islands.
Microsoft also has (mostly undocumented last I checked) APIs to accomplish the same thing on Win32 programs, as can be easily seen in explorer and powershell/cmd.
I think this change would make it look better on modern versions of Windows, even if it's entirely cosmetic.
The text was updated successfully, but these errors were encountered: