Is there a way to further increase the refresh speed of this widget?
At the moment it cannot go faster that 0.5 seconds (so called no limit). Is it possible to set it to 0.1 or even 0.01 seconds?
Is there a way to further increase the refresh speed of this widget?
At the moment it cannot go faster that 0.5 seconds (so called no limit). Is it possible to set it to 0.1 or even 0.01 seconds?
I don’t think that it can be done with the widget. However, if you want to monitor CPU core usage every 0.1 seconds, you could do it in a terminal:
htop -d 1
From htop --help
:
-d --delay=DELAY Set the delay between updates, in tenths of seconds
And with a little jiggery-pokery, the output could be fed to a Command Output widget to display it.
This is the type of situation where I miss the Plasma 5 Termoid widget:
The GitHub - koldbyte/termoid: Terminal in a Plasmoid page does show changes last year so it can be installed on Plasma 6 manually:
git clone https://github.com/koldbyte/termoid.git termoid
cd termoid
sh ./install
After installing, I was able to add the Termoid widget to the desktop. But I can’t get it working - it just displays the following message:
file:///home/scotty/.local/share/plasma/plasmoids/com.koldbyte.kde.termoid/contents/ui/main.qml:29:1: module “QMLTermWidget” is not installed
I also replaced qmltermwidget
from the repos (v0.2.0) with v0.1.0 as recommended on the Termoid GitHub & KDE Store pages:
sudo pacman -U https://archive.archlinux.org/packages/q/qmltermwidget/qmltermwidget-0.1.0-3-x86_64.pkg.tar.xz
But that didn’t fix the issue. I’m not going to look any further into it - I use Command Output for a lot of stuff anyway, and Yakuake provides a drop-down terminal on my desktop whenever I need it.
Hopefully @altman will find a solution that works for them.
Thank you @scotty65, I am afraid you put your hopes in the wrong person I’ll give it a shot I’ve been fiddling wih Conky but I didn’t have much success. Too many issues.
That would be too fast, I believe the code deliberately limit the minimum for safety reason (avoid system lockup). The code seems to rely on whatever QTimer restricts, though, it doesn’t limit the value on its own.