Also update the comment in each combobox item to be accurate for Plasma 5
Ideally, kcolorschemeeditor should be replaced with a new UI that is easier to use.
I'm adding Header color set support so that we can have a way to edit colors via a GUI in case the new color scheme editor doesn't make it into Plasma 5.21
In the port from the data engine several operations were subtly renamed
to match the new library method calls. This left them out-of-sync with
the existing config keys.
For distributions aiming to ship the Wayland session by default, allow
the Wayland session file to be installed as "plasma.desktop". Otherwise,
revert to status quo where the X11 session is installed as "plasma.desktop".
This script copies the old history to each activity.
This way the user has the previous history in each activity.
Also the launch counts get copied to the new location.
With the UI changes in Kicker and the logout screen over the past years
the concept of "leave" with a default shutodwn action has gotten muddy.
Kicker shows all the options explicitly, the logout applet has got left
behind, and is currently a bit broken. The leave option currently always
shutdown regardless.
It's perfectly valid to want to have a short applet shortcut to log out
sometimes, and shutdown in other times.
This patch adds explicit options for logout and reboot, and clarified
the UI presentation of shutdown to match what it currently actually
does.
BUG: 424426
BUG: 402081
In a Plasma Wayland session, kded does not use the XCB QPA and so Qt doesn't
have an X11 connection. For X11 windows, it has to set some properties on
registration to make them known, so just make an X11 connection in that case.
This was removed in
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/185,
however the original reasons for making the change no longer apply
because we now have a clean place to put the option--in the new popup
menu in the header. So let's re-add it, because hidden options are bad.
:)
BUG: 430017
FIXED-IN: 5.20
This is confusing since desktop icon sizes are set directly in the
desktop containment config window, and changing the desktop icon size in
this KCM has no visible effect at all. Let's not show it at all.
BUG: 429138
FIXED-IN: 5.21
I've seen popup being null when spamming notification removal.
Perhaps when the model already yanked the item under us before the Instantiator
had a chance to update its count... Not sure about the implications, but it
silences a warning I observed.
Right now for removable devices, the default action is either "Mount" or
"Unmount" (depending on whether you have automount turned on or off).
For the common case where you want to mount a device and then
immediately view its contents in the file manager, this requires a
two-step process: mount it, then expand the expandable list item, then
click on "Show in File Manager.
This commit changes the "Mount" action to "Mount and Open", collapsing
the three-step action into just one.
For people who really do want to just mount a disk without opening it, a
"Mount" action that does not also open the file manager is added to the
expandable section of the list item.
Additionally, because the "Show in File Manager" action that's already
in the expandable section of the list item would be redundant with the
one used as the primary action, it is now only shown for mounted
devices.
This mirrors a similar proposed change in the Plasma Vault applet:
https://invent.kde.org/plasma/plasma-vault/-/merge_requests/8
systemd provides a desktop diagnostic place for user to set environment
variables. Currently we only export to it but didn't import from it.
This would also import from it so we are able to use environment.d to
set environment even systemd unit based plasma is not used.
there was a behavioral change in qtvirtualkeyboard, where now it
reparents itself to the root item (done by purpose to make sure is
always on top of any overlay), not respecting the parent's geometry
so move it in the kwyboard widget itself
BUG:427934
closeSession returns only when the task is complete, a sound API, but we
need to remember to increase the timeout.
If a user has unsaved changes in kate, they could handle that prompt
after an indefinite period of time. We would still want to shutdown
afterwards.
Currently plasma-shutdown would abort if it thought ksmserver timed out.
Not seen in real life, just spotted in code review.
Doing so takes up extra space and I don't think it's useful information
anyway. If there's only one media player going, the user already knows
which one it is.