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
This one is actually a question, not a bug, I think.
I've been testing the library for a few days and now I wanted to replace the blue accent color with a yellow one. To do this, I´ve tried to use the color palettes defined in the file Dark\Palette.axaml and override the values.
Until I noticed that this has no effect. For example, I wanted to replace the blue focus border of the textbox. However, in the file Dark\TextBox.axaml no reference to a palette entry is set, but the color value is hard coded there again:
Yes, you are correct. palette is only used for reference, or people what to change some brush but still want to use predefined colors.
Semi definitely won't use shared brushes for different controls, thus user can override resources in minimum scope and minimum impact to other controls.
Meanwhile, I'm still hesitating whether we should use shared color for different brushes. I need to carefully consider this, and I can't leave you an answer now.
This one is actually a question, not a bug, I think.
I've been testing the library for a few days and now I wanted to replace the blue accent color with a yellow one. To do this, I´ve tried to use the color palettes defined in the file
Dark\Palette.axaml
and override the values.Until I noticed that this has no effect. For example, I wanted to replace the blue focus border of the textbox. However, in the file
Dark\TextBox.axaml
no reference to a palette entry is set, but the color value is hard coded there again:When I search for the hex value
54A9FF
, it is hardcoded in numerous controls.Is this the final way and the palettes are only a reference for developers, or will this being changed one day?
Or have I missed something maybe?
Thanks!
The text was updated successfully, but these errors were encountered: