The only way when an Item typed property would be false in boolean
context is when it is null anyway.

Regarding [].includes(), I stand by the point that QML engine should be
perfectly capable of optimizing such expressions in JIT down to a pair
of (>= && <=) checks -- given that enum members are continuous.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

This also fixes the plasmasearch KCM pretending to be changed when only the
KRunner specific options have been changed.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Fushan Wen authored May 26, 2022 and Nate Graham committed May 30, 2022

The panel focus shortcut is Meta+Alt+P. This keeps the old behavior.

BUG: 453166
FIXED-IN: 5.25
CCBUG: 352476

Aleix Pol Gonzalez authored May 20, 2022 and Aleix Pol Gonzalez committed May 29, 2022

It's the same components just in a different place. No need to do much
porting.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Luca Carlon authored May 27, 2022 and Nate Graham committed May 27, 2022

See the discussion in frameworks/plasma-framework!500.

BUG: 411462
BUG: 332512

Niccolò Venerandi authored May 27, 2022 and Nate Graham committed May 27, 2022

The "middle" variable  was not declared as var, and it raised an exception
when trying to set a value to it.

BUG: 454105
FIXED-IN: 5.25

This reverts commit 199ff3d4

Depending on layout's children is not reliable enough, because when
adding applets, one applet can be already in `appletsModel` but not in
the layout before the layout polish loop is finished.

childAt in currentLayout will return nothing when the initialization
process is still running, which will place the icon applet at a wrong
position and ruin the order of other applets.

BUG: 454105
FIXED-IN: 5.25

BUG:454175

BUG: 451422

FIXED-IN: 5.25

No longer implicitly included with KF deprecation level 5.94.

We are using the activities database just to load the list of
applications, no need to keep it alive forever.

In other access KCM we already call the executable directly using QProcess.

Task: https://phabricator.kde.org/T15468

GIT_SILENT

GIT_SILENT

childAt won't find any applet when adding a new preset panel
because all applets don't have a valid width during initialization.
But when replacing the leftmost/topmost widget with an alternative,
`childAt` also can't find any applet. The difference is when replacing,
layout's width is larger than 0 because other applets have valid
widths.

BUG: 453998
FIXED-IN: 5.25

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Victor Pavan authored May 18, 2022 and Nate Graham committed May 18, 2022

This makes the panel account for the change in size so that its minimum width or
height isn't too big.

BUG: 453102
FIXED-IN: 5.25

This calculates the distance between the start position to the edge
of the toolbar `startDragOffset`, and uses the offset to determine the
position of configDialog.

This also calculates `zoomFactor` to restore the relative mouse
position when the form factor of the panel is changed (horizontal
to vertical, or vice versa).

Using `onPositionChanged` instead of `onEntered` makes category change not so smooth (hard to notice sometimes though I got a number of such reports).

As `onPositionChanged` is used only to not to change category after scrolling end, this commit works around this problem and makes use of `onEntered`.

Xuetian Weng authored May 15, 2022 and Fushan Wen committed May 18, 2022

The group is expected to store a transliterated name.

Requires: plasma-workspace!1725

"Tablet Mode" is jargon that can confuse users. In this mode, things
become larger as an optimization for touch usage, but the word "tablet"
could easily refer to a drawing tablet, for which no touch
optimizations make sense.

Let's change the UI text here to call it "Touch Mode" instead.

Áron Kovács authored May 17, 2022 and Nate Graham committed May 17, 2022

Another popup menu seemed unnecessary when both buttons fit there.