Am Freitag, 18. November 2016, 15:16:21 CET schrieb Anton Aylward: > On 11/18/2016 02:10 PM, Patrick Shanahan wrote: > > * Anton Aylward <[email protected]> [11-18-16 12:48]: > >> On 11/18/2016 11:25 AM, Patrick Shanahan wrote: > >>>>> But its still a bit rough and I have no idea what the various CSS > >>>>> stanzas > >>>>> correspond to. That makes it difficult to fine tune. > >>> > >>> doesn't make much diff, as it will break with the next gtk3 update :( > >> > >> Perhaps that's why there is the darktable.css file which straps things > >> down > >> specifically for darktable across any/all changes that Gytk3 might make. > >> > >> That's how it now appears to be as I se it. > > > > iiuc, the problem is gtk3 changes break darktable.css, and they make no > > effort to announce inconsistancies or maintain any semblance of backward > > compatibility. Maybe they are getting under-the-table-support from m$. > > What you're implying, Patrick, is that darktable reads > /usr/share/darktable.css, then ~/.config/darktable/darktable.css and THEN > gos off and applies the Gtk3 on top of that. > > I would have thought that either darktable ignored the gtk3 or reads the > ~/.config/darktable/darktable.css last > > My experimentation certain has the ~/.config/ over-riding the /usr/share/
The important part is that darktable doesn't apply any CSS itself. darktable uses GTK which does the CSS handling. We tell it to load our CSS file (if ~/.config/darktable/darktable.css exists then that file is used, otherwise the global one). GTK then uses those values but some things are hard coded in the GTK theme itself which darktable has no control over. Tobias
signature.asc
Description: This is a digitally signed message part.
