We need to load the icon positions when screen geometry changes,
otherwise we risk using wrong geometry when screen is turned off or
otherwise changed, then saving the icon positions of that geometry.
For example, when turning off screen in single-monitor setup,
the resolution will change to 0x0. This then moves the icons around.
Then opening the screen doesn't move the icons, so the icons stay in the
0x0 positions, and save them to the "normal" resolution.
This fixes it by loading the positions whenever the geometries change
BUG:493569
Now everything in the header, main content view, and footer all use the
same consistent largeSpacing margins on all sides. Everything aligns
vertically even if you draw lines on a screenshot, and it looks amazing.
Part of https://invent.kde.org/teams/vdg/issues/-/issues/74.
Make them larger and consistent on the left, right, and bottom, which
looks better. And reduce them on top which centers the header text in
the space and makes the buttons respect Fitts' Law.
Currently we allow to remove any component, but they might reappear
again because the application re-registers them or the desktop file
is picked up again.
In most cases removing doesn't make much sense in the first place
since they are core system components that a user should not be
able to remove wholesale. They can unbind individual shortcuts
that are not wanted.
This introduces logic to determine whether a component should
be removable or not. For now it only coveres desktopfile-based
shortcuts since those are easier to deal with.
The logic is:
- Things in the System Services category cannot be removed
- Things in the Applications section can be removed if the
relevant desktop file has no shortcuts defined, i.e. the user
added it explicity
Dealing with runtime-registered shortcuts is left as a future
exercise
CCBUG: 452649
Due to PlasmaComponents.TextArea not having a context menu, change
the textArea to QQC2 one. This adds a working context menu.
BUG:427292
FIXED-IN: 6.2.0
The KCM widget and its children are destroyed before the KCModule.
Therefore by the time we call saveLayout the widget is already deleted
and accessing it crashes.
Instead save the layout right before the widget is deleted
BUG: 484690
SENTRY: SYSTEMSETTINGS-2D3
The power and session actions currently do not explicitly close kickoff
like starting an application does. In most cases this has no consequence
as kickoff will be closed by the session/power action itself or its
consequences. There are some, though, that do not necessarily do so; one
of them is sleep if the computer is configured to not lock the screen on
waking (otherwise locking would close kickoff).
This change makes the power/session buttons behave like regular entries
and close the popup when activated. The user can still prevent this by
pinning kickoff.
BUG: 493439
In AppletConfiguration, a connection is established to the signal
onSettingValueChanged of the loaded config page to enable the apply
button. If the page does not have such a signal, as is the case for most
if not all pages, an error message is printed every time that page is
loaded. This error is completely inconsequential (there are separate
mechanisms by which these pages control the apply button), so the
message is unnecessary and potentially misleading log spam.
This change sets the connection to ignore unknown signals, supressing
the error message. This is the same strategy also applied in
plasmoidviewer, see 9d29d6e9.
When an application can't handle a mimetype, now show an inline message
saying that it can't instead of a tiny enigmatic i icon,
also, show it immediately after selecting, intead of waiting apply has
been pressed
BUG:493527
This follows the HIG guidance that list items with 22px icons should
generally prefer the symbolic style. It makes Kickoff consistent with
all the other list items that use the symbolic style at this size.
BUG: 457077
FIXED-IN: 6.2.0
Co-authored-by: Noah Davis <noahadvs@gmail.com>
When recent document tracking is disabled, the kactivitymanagerd Stats
plug-in stops recording them in the SQLite database.
However, ResultSet will still query the database. If the user's home directory
is on an NFS share, this can lead to a noticeable delay when opening the
task manager context menu.
For this setup, it's best to disable recent document tracking as such
entirely, and skip querying the ResultSet in the first place.
It would also match user expectation to stop seeing recent documents
as soon as the feature is disabled.
Signed-off-by: Sebastian Stark <sebastian.stark@advantest.com>
Allows to watch the plug-in settings, such as scoring and recent documents,
via KConfigWatcher.
Signed-off-by: Sebastian Stark <sebastian.stark@advantest.com>
The window-list applet still uses the old location for the popup
placement enum (in PlasmaCore.Types), rather than its new home in
PlasmaExtras.Menu. As the old one is no longer defined, this may lead to
a misaligned popup menu, and definitely to a runtime error.
This change adapts the applet to the new way of accessing the popup
placement types.
kaccess uses the xcb Qt platform plugin which is dependent on xwayland from kwin running.
Without that Qt will fail to startup and kaccess will abort which can happen since systemd currently starts both in parallel.
Add an explicit `After` to the systemd unit file so that kaccess won't be started until kwin is running.
Signed-off-by: Reilly Brogan <reilly@reillybrogan.com>
