https://bugs.kde.org/show_bug.cgi?id=432254
David Redondo <k...@david-redondo.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/libksysguard/commit/f060 |ma/libksysguard/commit/679a
|0a7e53ba0792ffba190cb54c70c |24f373d7fa04ec279cedf95740b
|7aa1605fd |870efc9df
--- Comment #3 from David Redondo <k...@david-redondo.de> ---
Git commit 679a24f373d7fa04ec279cedf95740b870efc9df by David Redondo.
Committed on 02/02/2021 at 14:01.
Pushed by davidre into branch 'Plasma/5.21'.
Do the sensor setters in two stages
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.
(cherry picked from commit f0600a7e53ba0792ffba190cb54c70c7aa1605fd)
M +43 -16 faces/SensorFaceController.cpp
https://invent.kde.org/plasma/libksysguard/commit/679a24f373d7fa04ec279cedf95740b870efc9df
--
You are receiving this mail because:
You are watching all bug changes.
