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
Use systemPreferences.getAccentColor() #1
Comments
if you wanted to add this feature manaually you can get the color values from registry directly (check os first ofcorse) from this point
|
I did see your workaround. Are you doing any other manipulation on the hex value? I haven't tried it in code yet, but the Registry Editor value looks like it's stored as ABGR. Also interestingly enough, I tried to set the accent color in Windows 10 to #112233 via Settings and although that set the registry value correctly, if you choose custom color again in Settings it's showing me #1F3F5F |
@dotequals im not doing anything other than throwing the deciman value though toString(16), would you like me to upload the test project i showed in the video? also if you wanted i can invite you to my discord to try work somthing out? |
here you go, this is the project with the workaround repo my discord is also |
Oh thanks for that! I'll let you know if I run into any hurdles implementing it. I broke some core functionality which has taken priority. |
haha, thats the way it is, no worries if you need a hand i can see what i can do |
To continue our goal of more naturally conforming to a user's OS level preferences, we can read systemPreferences.getAccentColor() to set the accent color if it hasn't been deviated by the user (similarly to the dark mode stuff).
Like on macOS for dark mode, we would also want to listen for accent-color-changed.
Currently I believe this is roadblocked by this issue as the color seems to be slightly wrong even when automatic isn't enabled.
It's also unclear how compatible this is with older versions of Windows as I believe the accent color used to be very transparent on versions such as 7. Although
systeminformation
could probably be used to lock the feature to 10/8.The text was updated successfully, but these errors were encountered: