https://bugs.kde.org/show_bug.cgi?id=448675
--- Comment #5 from Trent M <twilightinz...@gmail.com> --- > Yes, we can do custom CSS but as far as I;m aware, it won't update at runtime > like we currently have; you'll need to restart your GTK apps to see changes. > Someone who's familiar with GTK needs to work on this to make it happen. I may be misinterpreting the intention of your reply here; the vibe I'm getting is that if we can't have hot-reloading, you don't feel that this issue is worth addressing anyways. I'm not inclined to think you actually feel this way. Lack of hot-reloading and needing to restart GTK applications so that they reload gtk.css is a small inconvenience compared to not having the theme follow your colors *at all*, unless you have one of those setups that automatically changes the colors periodically. But that type of setup is already broken by apps that can't use the colorreload module anyways. Anyways, for a fix for this issue to be submitted upstream to kde-gtk-config, what do you think would be better? Writing identical files to the gtk-4.0 directory at the same time as writing to the gtk-3.0 directory, or simply creating a symlink in the gtk-4.0 directory to the relevant files in the gtk-3.0 directory? Should this part of the discussion take place elsewhere? -- You are receiving this mail because: You are watching all bug changes.
