https://bugs.kde.org/show_bug.cgi?id=432220
--- Comment #7 from Sébastien P. ---
As you said, It is not fun. But it works.
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432220
--- Comment #6 from David Redondo ---
You are right in the CPU case where each core can go to 100% the maximum needs
to be 400% if you have 4 cores. But for memory since each value is part of the
same total we do not want to add it.
9 as the maximu
https://bugs.kde.org/show_bug.cgi?id=432220
--- Comment #5 from Sébastien P. ---
Not sure there is a maximum set for load averages, bandwith and CPU usage. I
wrote a nonsense here.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432220
--- Comment #4 from Sébastien P. ---
Created attachment 135356
--> https://bugs.kde.org/attachment.cgi?id=135356&action=edit
Manual scale
Hi David,
It is not possible to set manually the maximum because the manual maximum is
9 bytes. I can not g
https://bugs.kde.org/show_bug.cgi?id=432220
David Redondo changed:
What|Removed |Added
CC||k...@david-redondo.de
--- Comment #3 from David
https://bugs.kde.org/show_bug.cgi?id=432220
--- Comment #2 from Sébastien P. ---
Created attachment 135333
--> https://bugs.kde.org/attachment.cgi?id=135333&action=edit
A dirty patch…
My dirty patch… to detect the max scale. But it will probably fail in some
cases (which I do not have :/).
Bet
https://bugs.kde.org/show_bug.cgi?id=432220
--- Comment #1 from Sébastien P. ---
Probably this: https://invent.kde.org/plasma/libksysguard/-/merge_requests/48
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432220
Sébastien P. changed:
What|Removed |Added
Keywords||regression
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=432220
Sébastien P. changed:
What|Removed |Added
CC||sebastien.pica...@ovh.fr
--
You are receiving t
