~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon:wip/window-scales

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

edc5c78... by Alexander Larsson <email address hidden> on 2013-07-01

xsettings: Talk monitor scale into consideration when computing dpi

cd63777... by Alexander Larsson <email address hidden> on 2013-07-01

xsettings: Add support for window-scaling

We read the window-scale-factor gsettings and propagate to gdk, including doing
auto-detection if the setting is 0.

Additionally, we scale the old Xft.DPI setting by the window scale so that old
applications get a decent size on very high dpi monitors, plus we report the
unscaled dpi so that window scale aware apps (like gtk) can avoid this
dpi scaling.

bc2b4e2... by Marv-CZ on 2013-06-26

Updated Czech translation

6f49602... by William Jon McCann on 2013-06-26

xsettings: Remove settings for deprecated gtk-settings

a4c3299... by Jasper St. Pierre on 2013-04-24

power: Use a DBus property for screen brightness

A property is easier for clients to manage, as they'll automatically
get new PropertiesChanged signals when the value changes, and with
GDBus bindings, properties are cached field lookups that don't require
asynchronous access.

If there are any errors when fetching the new brightness, the value
-1 is returned, so the interface has been modified slightly to support
signed values.

Also adapt the color and media-keys plugins to the new interface.

https://bugzilla.gnome.org/show_bug.cgi?id=698754

9763448... by Jasper St. Pierre on 2013-06-12

power: Split out get_property

We want to add properties on the Screen iface, so remove this.

https://bugzilla.gnome.org/show_bug.cgi?id=698754

26acadd... by Bastien Nocera on 2013-06-17

3.9.3

b045ab3... by Bastien Nocera on 2013-06-17

main: Remove generated script on clean

6b463f7... by Bastien Nocera on 2013-06-14

power: Update time_to_empty/time_to_full from the real batteries

So that we use upower's knowledge of that value instead of making
up our own. This fixes the test_action_critical_battery test failing.

https://bugzilla.gnome.org/show_bug.cgi?id=700913

eedfa80... by Jasper St. Pierre on 2013-05-22

power: Make GetPrimaryDevice always return the composite device

With one battery, the composite device should report what we want as
well, so this shouldn't see any major changes in most cases. The reason
this is wanted is so that when the device is charging or fully charged,
we'll get the composite device as well, rather than throwing an error.

https://bugzilla.gnome.org/show_bug.cgi?id=700913