-
-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dark theme doesn't work on Win 11 #743
Comments
@gerroon @tvmole @Gitofthelawn can you please check if this still happens in 2.0.16 or the latest pre-release? https://github.com/ransome1/sleek/releases/tag/v2.0.17-rc.4 |
I still have the issue with 2.0.17, even after deleting the user data folder. I use some other electron based apps, and they all respect the dark theme preference even without explicitly telling the app to use dark theme. I also use Sleek on a Win10 PC, that one respects the dark theme setting. So it seems to be a Win 11 thing. |
@gerroon I now do have access to a Windows 11 virtual machine. Unfortunately it is a development version which does not allow to switch to dark mode. So I need you to help me out again here. I have done some refactoring and I hope it solves the issue you're having. You can download the latest version here: https://github.com/ransome1/sleek/releases/tag/v2.0.19 If sleek's theme setting is set to system, it automatically adjusts to the OS theme. If you choose either dark or light theme, it persists to either of it. If you are experiencing anything else the bug is still present. |
Bug Report
Important
Please follow this template strictly when reporting bugs.
Reports that do not adhere to this template will not be addressed and will be closed.
App Version: Enter the version number, e.g., 1.2.3
2.0.14
Platform: Windows / macOS / Linux
Win 11
Installation Method: App Store / Direct Download / Other
Zip
Expected Behavior:
The app should use dark theme
Actual Behavior:
It is using light theme
Steps to Reproduce:
settings
set to dark theme
restart
Screenshots:

The text was updated successfully, but these errors were encountered: