Now users can modify LC_ADDRESS, LC_IDENTIFICATION, LC_NAME and LC_TELEPHONE from region settings.
See LC_IDENTIFICATION example here: https://lh.2xlibre.net/locale/fi_FI/
BUG: 204525
BUG: 430801
While we indeed write both with KConfig::Notify flag interested
processes might only listen to the scheme change instead of
every color scheme group. When they react to the scheme change
the colors have not yet changed.
The colors kcm also does it in this order.
BUG:421745
FIXED-IN:5.24.7
Most people don't have their latitude and longitude memorized. It is
*far* easier for people to point out their approximate location on a
map, than to look up their latitude and longitude online.
This also removes the need for a "Detect Location" button there.
Both coordinates being exactly zero indicates that location data is still
loading. So show loading text instead of spurious coordinates and calculated
timings.
This merge request adds support for additional Global Theme layout settings to
be set in KCM, if the selected theme supports them:
- (controlled by Desktop Layout switch) Borderless Maximized Windows
- (own switch) Titlebar Buttons Layout
Ones with their own switch also have new checkboxes for themselves in More Options in
the KCM, and the values for all the added options, in the new `layouts/defaults` file
of Global Themes, are made to match their KDE Plasma config files counterparts in names
and values.
Example of a `layouts/defaults` file in a Global Theme:
```
[kwinrc][org.kde.kdecoration2]
ButtonsOnLeft=M
ButtonsOnRight=IAX
[kwinrc][Windows]
BorderlessMaximizedWindows=false
```
NOTE: If a Global Theme doesn't supply `BorderlessMaximizedWindows`, it'll be turned off automatically when applying a Desktop Layout to prevent issues.
Before, NumberField displayed 6 decimal digits for the coordinates, which
implies centimeter-scale resolution, which is of course not the case.
Now it shows 2 decimal digits, which is reasonable and consistent with the
level of precision shown in Automatic mode.
Currently we are very inconsistent with how we handle our various X11 dependencies.
Some places check whether specific sub-libraries are found and disable parts of the code accordingly.
Sometimes this is controlled by whether X11 is found at all, sometimes it depends on the sublibrary being present.
Some of this is obviously broken, e.g. in one like we check whether X11 is there and then use it unconditionally a few lines down.
Instead of the current system of optional deps and deps being conditional on other deps I propose that we introduce an explicit build option that controls the X11 support.
If on (the default) then all X11 libs are required.
If off then no X11 libs are searched for. Currently this results in a broken build since some places use X11 stuff unconditionally, but it gives us an easier way to test and fix those cases.
Setting unchanged values may falsely trigger an authentication
prompt in the case that the changed value doesn't need authentication
to change, but the unchanged ones do, leading to an authentication prompt
to show up.
Adding a little bit of original vs new comparison lets us only send over
DBus what got changed.
BUG: 437286
PreviewWidget has a timer that advances to the next frame of the current
cursor.
"current" can change in setTheme, we need to stop the animation timer
BUG: 456526
Akseli Lahtinen
l10n daemon script
Nicolas Fella
Volker Krause
David Redondo
Bharadwaj Raju
Dominic Hayes
Han Young
Alexander Lohnau
Jan Blackquill
Ahmad Samir
Aurélien Couderc
ivan tkachenko
Tanbir Jishan
Weng Xuetian
David Edmundson
Nate Graham
Devin Lin