<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: fix fontconfig monitoring" href="https://bugzilla.gnome.org/show_bug.cgi?id=786694#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: fix fontconfig monitoring" href="https://bugzilla.gnome.org/show_bug.cgi?id=786694">bug 786694</a> from <a href="page.cgi?id=describeuser.html&login=bugzilla%40hadess.net" title="Bastien Nocera <bugzilla@hadess.net>"> Bastien Nocera</a> <pre>The XSettings in the xsettings plugin are either: - in GSettings, and GTK+ will read those directly under Wayland - hardcoded in gnome-settings-daemon, for older versions of GTK+, and hardcoded in newer versions of GTK+ 3.x - "computed" in the xsettings plugin Those last ones are what we're interested in here. They are: - fontconfig timestamps (Fontconfig/Timestamp) - whether to enable animations (used for remote displays, Gtk/EnableAnimations) - GTK+ modules list (Gtk/Modules) - whether gnome-shell (and its builtin menu) is running (Gtk/ShellShowsAppMenu) - a number of font and DPI settings (see xft_settings_set_xsettings()) That last two are handled directly in GTK+ in Wayland talking to the compositor and checking its capabilities, or in gdk/wayland/gdkscreen-wayland.c. Which leaves us with those first 3 settings (for now). So, on top of the fontconfig specific changes above, it would be nice if: - the D-Bus name showed that the settings are GTK+ specific, say "org.gtk.Settings" - also export Gtk/EnableAnimations and the modules list through D-Bus</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>