Now they use the right service and sensor names

BUG:433169
FIXED-IN:5.21.2

Ahmad Samir authored Feb 19, 2021 and Arjen Hiemstra committed Feb 26, 2021

All other KWindowSystem::windowChanged(WId, uint) has been deprecated
since KF 5.0.

Some sensors have a range of gigabytes or terabytes, like memory and
disk. Since the base unit for these is bytes, we end up needing a very
large value in the range, which currently is not possible due to the
spinbox limiting the value. Internally, spinbox seems to use an int so
we can only store a value that fits within the range of an int, so we
use that as min/max value.

Longer term we want to have some ability to choose an actual "maximum"
sensor but that's going to need more work.

BUG: 433007
BUG: 424527

We do not necessarily have a config loader (invalid id or when the face does
not have any config options).
BUG:433431
FIXED-IN:5.21.1

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"

getQModelIndex can return an invalid index. If that happens, we emit
dataChanged for an invalid index, which is incorrect and may cause
errors in other models.

CCBUG: 431155

When the pie chart gets smaller, we now hide certain parts of the text
to ensure things are not peeking outside the pie chart. This prevents
glitches when used in a Plasma panel for example.

BUG: 431995

This was missed when initially implementing the support

CCBUG: 431995

This returns true if the root is pointing to a valid path. The idea
being that non-systemd systems won't have applications scoped correctly,
nor a relevant user slice.

By communicating this we can dislpay the entry as not working in the UI.

With an update rate of 500ms the history amount of 300 seconds ends up
with 600 items. With very variable sensors like CPU usage or network
usage, this is not very useful, so reduce the history amount to 60
seconds as default.

When saveConfig() in ConfigSensors.qml is called we started resolving sensors,
when during this time loadConfig() was called we returned the old sensors, which
when then triggeded another saveConfig() call by  plasma-systemmonitor leading us to
effectively reset ourselves.
The setters are now in two stages, during resolving time we set the properties
to the unresolved value, so we are in sync with what the qml part did. Also we not
do another resolve when something tries to set the current unresolved ids.
BUG:432254

This makes it easier to build against both Qt5 and Qt6

GIT_SILENT

Otherwise we do not get a correct minumum/maximum value when those get
updated later on.

The minimum and maxmimum properties only change when the sensor metadata
changes, so we can cache them and avoid some extra work when they get
queried repeatedly.

When our cgroup PIDs are changed, potentially all columns are changed.
The existing dataChanged only handled the first column

Formatter has an option to return "" when null is passed as a value.
This patch also treats NaN is null.

Typically this only happens during loading conditions.

update calls a virtual method to filter for valid cgroups, it is important
this is not called during the constructor.

Deferring this also helps speed up loading this model. Any view already
handles data being updated afterwards.

An upcoming systemd change puts all services in the app slice by default. We don't
necessarily want to list all of these as applications.

In certain cases, we may end up with a dirty config which we do not want
to store. So explicitly cleanup the config objects before destruction to
prevent them from being written.

BUG:428970

This was showing in hotspot as 14ms per update.

It turns out QDir creates a full QFileSystem entry on every file, even
using QDirIterator and with all features turned off.

This isn't really useful when iterating through /sys which has simpler
requirements.

Using a lower level API brings that down to 2ms.

GIT_SILENT

GIT_SILENT

GIT_SILENT

GIT_SILENT

Before we would block until one DBus call for each entry in the
requested sensor array was finished.

SensorFace defaults don't need cascading and globals

Otherwise it will trigger two processes updates

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"

With the changes to have an API that determines what the update rate is
for sensors, it now becomes rather awkward to specify the number of
items a line chart should keep, since this number is dependant on the
update rate. So instead, change the line chart to have a single
configuration value indicating how much history to keep, in seconds.
This is then converted to a number of items based on the current update
rate of the sensor.

This indicates the model has loaded the metadata for the current sensors
and thus querying metadata properties for these sensors will not return
invalid results.

This allows us to change things to read the update rate from sensors
rather than needing to hardcode this. Right now the value for Sensor and
SensorDataModel is hardcoded to 500ms, which matches the new update rate
of KSystemStats. However, this new API allows us to change this without
needing to update everything else in the future.