localed will not update the LC_* variables if they are not given. This
means that should the user switch the formats away from LANG and then
back, they will not be reset appropriately.
Simply always setting the variables even if the match will fix this.
Instead of using @borders for drag handles, we use @theme_fg_color at 40% opacity. Because these are widgets intended to be interacted with by users instead of drawing borders, we should use a semantically appropriate color which updates according to whether a user has a dark theme selected or not. This ensures that the drag handles contrast with the background no matter what stylesheet the user is using.
This improves the contrast of these widgets in the light theme from 1.7:1 to 2.9:1, which is still rather low, but greatly improves the usability of these widgets without having too large an impact on the look of the widgets in-situ. The contrast ratio is unchanged in the HighContrast style (4.0:1).
This also improves the situation if we eventually adopt a dark style preference for users, and improves the portability of the application.
For the "development" profile, lets use the Nightly variant, to
visually indicate to users that they are running an unstable
version of the application.
Since 4.10, Samba supports python3. Therefore we updated "Samba"
here. That required us to bundle lmdb since it is a samba build
dependency. See
https://wiki.samba.org/index.php/Samba_4.10_Features_added/changed
We also disable pam and json to speedup the build and require
less bundled dependencies.
intltool has been removed from the SDK and the release-team has
advised users to bundle it in their Flatpaks until the dependencies
get ported away from it. See
https://mail.gnome.org/archives/desktop-devel-list/2019-August/msg00000.html
This patch also ships with some polkit changes to make it suitable
for use within Flatpak. These changes were copied from gnome-builder.
Add a scheme to the address which we test for correctness
by g_network_address_parse_uri(). It does not work without it.
Use "none" scheme if user did not entered one.
Use port number 0 if user did not specify any.
Fixes#679
Empty is a valid value here. It means the setting is not set. Two places
need to be updated:
- the validation function
- when retrieving the value from the combo, empty strings need to be
mapped to a setting value of NULL
Closes#677
"Primary Display" and "Contains top bar and Activities" are visible when
you have >1 display connected and the "Join Displays" option is
selected. I can't work out how to see the "Active Display" string but it
sure looks translatable to me.
