-
Notifications
You must be signed in to change notification settings - Fork 194
Some times primaryColor and accentColor are not used #37
Comments
Post your custom theme. |
|
Remove color primary/primarydark/accent from your theme and leave just text color. Don't re-set values Colorful is already setting. |
When I remove color primary/primarydark/accent from the theme, but now color of the interface are not using ThemeColor.GREEN and ThemeColor.BLUE, now color is the default color of "Theme.AppCompat.Light.NoActionBar". |
Ah I see your problem. Remove the parent item. When you're merging a style don't use a parent theme because then you will override all the values Colorful just set. |
When I remove the parent item, the default color is now correct. But when I dynamically change
|
Hmm. This seems like just weirdness with Android's style engine. What happens if you use a custom base theme instead of a override? Note you'll need a parent theme to do the base theme. The order of operations for Colorful is Base Theme -> Colorful Colors -> Custom Override Latter overrides the former. |
After switching themeBefore switching themeCodeApplication.kt
MainActivity.kt
Style.xml
|
I've been very busy and haven't gotten time to test this yet, but I plan on testing if I can reproduce this tonight. |
@garretyoder I want to use "customTheme", because only in this way can I change
textColorPrimary
color, but nowprimaryColor
andaccentColor
are not used, this may be misunderstood, but these two values are non-null.The text was updated successfully, but these errors were encountered: