The way we’ve implemented this is that we always query all named colors, regardless of what change notification we receive. So even if a color theme change wouldn’t trigger a notification, a subsequent accent color change (that you observe) should pick up the changed fg/bg colors.
Sounds like an issue with GTK or the underlying shell bindings. One way to test this hypothesis could be to write a simple GTK program that exercises the gtk_style_lookup_color API after a theme change. Christopher Schnick <crschn...@xpipe.io> schrieb am Fr. 28. Feb. 2025 um 21:01: > The only change that is registered when I switch between dark mode > settings is: > replaced Yaru by Yaru-dark at key GTK.theme_name > > If I change the accent color, it registers the following changes: > replaced 0xe95420ff by 0x03875bff at key > GTK.theme_unfocused_selected_bg_color > replaced 0xe95420ff by 0x03875bff at key GTK.theme_selected_bg_color > replaced Yaru by Yaru-viridian at key GTK.theme_name > > It seems like this is very much limited to the foreground and background > colors not updating. The fg and bg color is also not updating when > restarting the application or even rebooting. I switched to light mode, > rebooted, and it still reports dark mode. > > On 28/02/2025 14:49, Michael Strauß wrote: > > Are colors reported at all in the change notification on your system? > > If not, then it's probably because gtk_style_lookup_color() returns > false. >
