The default value for active in the kcfg file inside kwin for colour
correction is false.
As we have a bridge that mirrors the config contents over DBus and
defaults hardcoded in a second format this has got out of sync.
This both leads to the default button being enabled/disabled incorrectly
on a fresh system and not working properly.
More important as geo-location is on by default this leads to http
requests being made without the user's explicit consent. A major bug.
BUG: 442253
Works around the usual case of Breeze / Oxygen ensurePolish coming too late
causing a menu with an unwanted black outline, even more noticeable with Oxygen.
The next Plasma release (5.23) will be promoted and publicly referred
to as "Plasma 25th Anniversary Edition". This adds a subtle hint to
that to the splash screen.
It's a bit odd to have a "Save As..." Button but no "Save" button. The
"Apply" Button does the same thing that a save button would, and is
active during the same times, so let's just make it *be* a "Save"
button.
CCBUG: 411317
Currently they live in the Breeze repo which is a bit weird and random
and complicates the process of updating the default wallpaper. Let's
centralize them all to live here.
Use image sizeInBytes
Use Qt:endl
register qml with qml register anonymous type
Remplace QDrag start by QDarg exec
QModel acces, remove use of child
Use QFileinfo, use birthTime()
Use QRandomGenerator
This commit adds several keywords to system settings' various options like Fonts,
Autostart, Colors, Formats, Themes etc. so that users are able to search these
options easily from the system settings.
Plasma had an entire text editor for the script engine in process.
The method for loading this was very convoluted, it loaded a QML file
(in plasma-desktop!) which contained an Item(!) which then loaded a QML
component that showed a widget dialog.
It also means loading a very heavy lib KTextEditor in ShellComponents
which is very heavy. This will get loaded in things like the logout
greeter, which is super slow on the pinephone.
We already had the concept of evalating a script remotely, we can just
hook up the print statement and move the whole executable out.
Technically this is an API break on the plasmashell DBus API, but
pragmatically going from void -> something on the return type isn't
going to break anything.