SUMMARY KDE Plasma 5.18 had the option to decrease the interval in seconds. This option has disappeared with the new widgets in version 5.19. There's only a fixed interval time implemented now. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.19.3
What particular widget are you talking about?
All of the system monitoring widgets (and these are the only ones I checked/use): memory usage, cpuo usage, drive activity, network activity.
Yes it changed. Can you expand on why it was useful to set an interval?
Created attachment 130328 [details] attachment-18905-0.html It was useful for me to reduce the load on the machine and because it wasn't necessary for me to have such frequent updates of the statistics. David Edmundson <bugzilla_noreply@kde.org> schreef op 23 juli 2020 11:05:53 CEST: >https://bugs.kde.org/show_bug.cgi?id=424561 > >David Edmundson <kde@davidedmundson.co.uk> changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > CC| |kde@davidedmundson.co.uk > >--- Comment #3 from David Edmundson <kde@davidedmundson.co.uk> --- >Yes it changed. > >Can you expand on why it was useful to set an interval? > >-- >You are receiving this mail because: >You reported the bug.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
My reason for asking is I've turned things into a polling based API to an event-driven on-change API, which in theory should lower the CPU hit. Also by moving it to the backend rather than the UI we can apply something more sensible defaults like only fetching disks every few minutes, whereas CPU info is a lot more dynamic. So it was deliberately done to try and tackle this at the root for everyone. If there's any specific feedback on things no really working we can of course address that.
Alright, in that case it should be fine.