Yasp-Scripted (Systemmonitor) v1.0.8a

Plasma 4 Widgets

Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net

24
8.2
Description:

Yes, Yet another systemmonitor plasmoid.
But still different from the others.
The only useful plasmoid systemmonitor i have found was Yasp. The problem with it was that it was not configurable enough.
So I came up with the idea, that everyone has its own imaginations of what belongs into a systemmonitor and what not. The birth of Yasp-scripted.
The name is similar to Yasp, because I use some modified code from that project.
The biggest advantage is that you can add things to the monitor or remove some, by just changing the script file and reparse it again...) No recompilation or something like that needed...
The scriptfile which comes with this applet is a scriptfile which fits exactly my system. You probably need to change it to fit your system (e.g. if you do not have a wireless lan card, you need to remove the wlan stuff from the script file).

You can send me your script, such that I can upload a whole bunch of scripts, the user could choose of later (maybe with a screenshot to see directly what the script does)

The scripts can be found in the directory yasp_scripts.
The 1st screenshot is systemmonitor_by_mtr.script, the 2nd screenshot is systemmonitor_by_patkoscsaba.script
and the 3rd screenshot is the script collection by duncan
(thx for the scripts).

If you want to align things, you should either use a monospace font, or use a t in the value.

If you are familiar with svg you maybe will create your own svg's for the bar-meter. Send them please to me to have a wider range of look and feel for the system monitor ;)
Last changelog:

8 years ago

1.0.8a - wrong folder prefix ;)

1.0.8 - bug fixed when reparsing (the kde-plasma-handle was deleted, but we should not delete it)

1.0.7 - bug fixed if engine-sensors contains a colon
- Added script by joseph (thx for the script)
- New script by aldo (thx for the script)

1.0.6 - stack keyword added to plotter (thx Chris99 for the patch)
- Script by mtr added (thx for the script)

1.0.5 - fix crash on reparsing in kde-4.5.2 (with 4.5.2 reparsing works again, but 4.5.1 and 4.5.0 have a bug)

1.0.4
- Label preferredSize setting correctly + sizePolicy changed

1.0.3
- meter sizePolicy changed (works now better in KDE-4.5)
- bugfix for KDE-4.5 such that it does not crash on removal

1.0.2
- workaround for problems with KDE-4.5 and meters (min_height parameter added)
- added script by aldo to the package (italian labels)
(- known issue: yasp-scripted crashes on reparsing in kde-4.5. This will be fixed in a later release)

1.0.1 - bug fixed if yasp is closed while parsing the script

1.0: - Reparsing should be more stable

dovidhalevi

9 years ago

There is something just like this (if I could only remember the name!!). NOT a plasmoid though I posted to plasma-developers about making it into a plasmoid. Very similar scripting, everything but the kitchen sink. So ... reinvented the wheel, not so horrible :-)

1. Everything in plasmoids needs be asynchronous. If it is "waiting for" something, plasma will hangup waiting. Your implementation may in fact be OK, but should pass the wait after a short! time, leave field blank (as the above app did).

2. Most any attempt to live-edit the script and reparse crashes plasma. So no way to try and fix scripts. The above app was well behaved doing this (did not crash itself and of course did not touch plasma).

I am looking for a ksensors replacement so a better system monitor is the best idea.

Report

DuncanKDE

9 years ago

> There is something just like this
> (if I could only remember the
> name!!).

Maybe superkaramba? FWIW plasma supports superkaramba themes now too. =:^)

But superkaramba is a bit more complex to learn (because it's a bit more powerful). Yasp-scripted is indeed very similar, but doesn't have the widget positioning bits as it simply reads the scripts top to bottom and places the widgets vertically in order as it reads them. To get multiple columns with yasp-scripted, you use multiple instances of the applet (as I did for the scripts and screenshot I contributed). As I didn't know superkaramba's scripting language yet and was looking for a solution I could get up and running with on kde4 (since there's no ksysguard kicker applet replacement and the kde4 app formerly known as ksysguard, itself, is terribly buggy at restoring settings), yasp-scripted was easier for me to start with, tho I expect I'll at least try superkaramba some time in the future, and keep to it when I do unless it has worse performance.

> 1. Everything in plasmoids needs be
> asynchronous. If it is "waiting for"
> something, plasma will hangup
> waiting. Your implementation may in
> fact be OK, but should pass the wait
> after a short! time, leave field
> blank (as the above app did).

That was indeed an issue at one point. I /think/ it has been fixed now. Well either that or I got the bugs in my scripts worked out. Probably a bit of both. =:^)

> 2. Most any attempt to live-edit the
> script and reparse crashes plasma.
> So no way to try and fix scripts.

That does remain somewhat of an issue, but it doesn't mean there's no way to edit/fix the scripts. Presumably, someone advanced enough to know how to do their own scripts in the first place can figure this out, but FWIW, krunner is entirely separate from plasma, as is khotkeys. Actually, due to plasma not yet having temporary panel retract buttons like kicker did and the hassle of reconfiguring panels just to get them out of the way when necessary, I deliberately killall plasma-desktop at times, and simply use krunner and khotkeys for invoking apps, until I'm done with whatever I wanted the panels out of the way for and can restart plasma-desktop (using the same krunner or khotkeys mechanisms).

Thus, when I made a mistake in a yasp-script (plotter using a sensor that wasn't there, due to a typo in the name) and it was triggering plasma-desktop crashes, I simply launched my editor using either krunner or khotkeys (IDR which), and did my editing from there. Of course, I could launch plasma-desktop to test my changes the same way.

As I said, while some users may find this challenging, in general it shouldn't be rocket science for the types of users already advanced enough that they're doing their own scripts.

> I am looking for a ksensors
> replacement so a better system
> monitor is the best idea.

I know the feeling. It'd have been great if there was a plasmoid to parallel the ksysguard kicker applet from kde3 -- and of course if the application formerly called ksysguard (in kde3, in kde4 called the so generic it entirely fails as a proper app identifier, system monitor) wasn't so buggy in kde4. I expect the latter will eventually be fixed, but with kde dumping kde3 support well before kde4 was up to replacing it, I didn't have luxury of being able to wait for that, unfortunately.

Yasp-scripted stepped in to fill the gap (and then some!). =:^) Of course, superkaramba would have done so and been even more powerful, but its additional complexity (even if that brings additional power as well) was a bit much to take on at a time when I was already spending way more time working on the upgrade from kde3 than I expected, and than I would have spent if kde had continued to support kde3 until kde4 was an appropriately stable and mature replacement for it. Unfortunately, they didn't, but fortunately, yasp-scripted was there when I needed it. =:^)

Report

C

finkandreas

9 years ago

The app you mean is probably conky... And yes it has even more functionality than this plasmoid. And yes it uses far less resources than this plasmoid.
However conky is not a plasmoid and therefore does not have the look of a plasmoid. And it has the drawback that you can plot only one value into a plotter...
But you're right, the idea is quite similar, whereas conky is built for speed (therefore a lot of different options are available and for almost any information there are builtin functions in conky), and this plasmoid was just a little project of mine, with absolutely no optimizations ;)

And I do not think that this plasmoid is waiting anywhere for a process to finish (at least it does not wait actively for it, but in the background), so plasma should not stop working because of this plasmoid?

Report

xaghor

9 years ago

all is right, it works ! thank you

Report

xaghor

9 years ago

Hello

I have one problem with compilation's script and I dont understand what is the problem. If somebody could help me please....
I have kubuntu 9.10 x64 ans I have already installed kdelibs5-dev,build-essential,cmake, libphonon-dev but I have one error in compilation :

xaghor@xaghor-kubuntu64:~/Desktop/yasp-scripted-0.99a$ #Release
xaghor@xaghor-kubuntu64:~/Desktop/yasp-scripted-0.99a$ mkdir build
xaghor@xaghor-kubuntu64:~/Desktop/yasp-scripted-0.99a$ cd build
xaghor@xaghor-kubuntu64:~/Desktop/yasp-scripted-0.99a/build$ cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` -DCMAKE_BUILD_TYPE=release ../
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found.
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found.
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found.
-- Found Qt-Version 4.5.2 (using /usr/bin/qmake)
-- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so
-- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found X11: /usr/lib/libX11.so
-- Looking for include files CMAKE_HAVE_PTHREAD_H
-- Looking for include files CMAKE_HAVE_PTHREAD_H - found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found Automoc4: /usr/bin/automoc4
-- Found Perl: /usr/bin/perl
-- Phonon Version: 4.3.1
-- Found Phonon: /usr/lib/libphonon.so
-- Found Phonon Includes: /usr/include/qt4/KDE;/usr/include/qt4
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_FPIE_SUPPORT
-- Performing Test HAVE_FPIE_SUPPORT - Success
-- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL
-- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success
-- Performing Test __KDE_HAVE_GCC_VISIBILITY
-- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success
-- Found KDE 4.3 include dir: /usr/include
-- Found KDE 4.3 library dir: /usr/lib
-- Found the KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler
-- Found automoc4: /usr/bin/automoc4
-- Configuring done
-- Generating done
-- Build files have been written to: /home/xaghor/Desktop/yasp-scripted-0.99a/build
xaghor@xaghor-kubuntu64:~/Desktop/yasp-scripted-0.99a/build$ sudo make install
[sudo] password for xaghor:
Scanning dependencies of target yasp_scripted_automoc
Generating scriptparser.moc
Generating yasp-scripted.moc
Generating frame.moc
Generating label.moc
[ 0%] Built target yasp_scripted_automoc
[ 12%] Generating ui_config.h
Scanning dependencies of target yasp_scripted
[ 25%] Building CXX object CMakeFiles/yasp_scripted.dir/yasp_scripted_automoc.o
[ 37%] Building CXX object CMakeFiles/yasp_scripted.dir/yasp-scripted.o
/home/xaghor/Desktop/yasp-scripted-0.99a/yasp-scripted.cpp: In constructor ‘Yasp::Yasp(QObject*, const QVariantList&)’:
/home/xaghor/Desktop/yasp-scripted-0.99a/yasp-scripted.cpp:56: error: invalid use of non-static member function ‘bool QFont::bold() const’
make[2]: *** [CMakeFiles/yasp_scripted.dir/yasp-scripted.o] Erreur 1
make[1]: *** [CMakeFiles/yasp_scripted.dir/all] Erreur 2
make: *** [all] Erreur 2
xaghor@xaghor-kubuntu64:~/Desktop/yasp-scripted-0.99a/build$


thanks

Report

C

finkandreas

9 years ago

that's strange... Something is wrong with your compiler... However the lines 56 and 57 (in yasp-scripted.cpp) are irrelevant for this plasmoid (i forgot to delete them). You can safely delete these two lines, and try to recompile.

Report

xaghor

9 years ago

could you give me what are the lines I must delete please, to be sure... thanks

Report

C

finkandreas

9 years ago

yasp-scripted.cpp:56
QFont f("Times", 15, QFont::bold);
yasp-scripted.cpp:57
qDebug() << f.toString();

These two lines can be safely deleted...

Report

xaghor

9 years ago

thanks, it's better, that's resolve this error ! but a new error appears after... this this the new logout :

Scanning dependencies of target yasp_scripted_automoc
Generating scriptparser.moc
Generating yasp-scripted.moc
Generating frame.moc
Generating label.moc
[ 0%] Built target yasp_scripted_automoc
[ 12%] Generating ui_config.h
Scanning dependencies of target yasp_scripted
[ 25%] Building CXX object CMakeFiles/yasp_scripted.dir/yasp_scripted_automoc.o
[ 37%] Building CXX object CMakeFiles/yasp_scripted.dir/yasp-scripted.o
[ 50%] Building CXX object CMakeFiles/yasp_scripted.dir/frame.o
[ 62%] Building CXX object CMakeFiles/yasp_scripted.dir/label.o
/home/xaghor/Desktop/yasp-scripted-0.99a/label.cpp: In member function ‘virtual void Label::mousePressEvent(QGraphicsSceneMouseEvent*)’:
/home/xaghor/Desktop/yasp-scripted-0.99a/label.cpp:100: warning: ignoring return value of ‘int system(const char*)’, declared with attribute warn_unused_result
/home/xaghor/Desktop/yasp-scripted-0.99a/label.cpp:103: warning: ignoring return value of ‘int system(const char*)’, declared with attribute warn_unused_result
[ 75%] Building CXX object CMakeFiles/yasp_scripted.dir/scriptparser.o
/home/xaghor/Desktop/yasp-scripted-0.99a/scriptparser.cpp: In constructor ‘ScriptParser::ScriptParser(Yasp*)’:
/home/xaghor/Desktop/yasp-scripted-0.99a/scriptparser.cpp:40: error: ‘cout’ is not a member of ‘std’
/home/xaghor/Desktop/yasp-scripted-0.99a/scriptparser.cpp:40: error: ‘endl’ is not a member of ‘std’
make[2]: *** [CMakeFiles/yasp_scripted.dir/scriptparser.o] Erreur 1
make[1]: *** [CMakeFiles/yasp_scripted.dir/all] Erreur 2
make: *** [all] Erreur 2

...

Report

C

finkandreas

9 years ago

just download new 0.99b version... It seems like I packaged an old directory with some debug output, which was only for me interesting...
That should work for you...

Report

C

finkandreas

9 years ago

is $HOME/.yasp.script a file, or a directory on your pc? It should be a file, namely the scriptfile you want to use for this plasmoid.

Report

xaghor

9 years ago

I have downloaded the new version. The compilation ends with this output :

Scanning dependencies of target yasp_scripted_automoc
Generating frame.moc
Generating yasp-scripted.moc
Generating scriptparser.moc
Generating label.moc
[ 0%] Built target yasp_scripted_automoc
[ 12%] Generating ui_config.h
Scanning dependencies of target yasp_scripted
[ 25%] Building CXX object CMakeFiles/yasp_scripted.dir/yasp_scripted_automoc.o
[ 37%] Building CXX object CMakeFiles/yasp_scripted.dir/yasp-scripted.o
[ 50%] Building CXX object CMakeFiles/yasp_scripted.dir/frame.o
[ 62%] Building CXX object CMakeFiles/yasp_scripted.dir/label.o
/home/xaghor/Desktop/yasp-scripted-0.99b/label.cpp: In member function ‘virtual void Label::mousePressEvent(QGraphicsSceneMouseEvent*)’:
/home/xaghor/Desktop/yasp-scripted-0.99b/label.cpp:100: warning: ignoring return value of ‘int system(const char*)’, declared with attribute warn_unused_result
/home/xaghor/Desktop/yasp-scripted-0.99b/label.cpp:103: warning: ignoring return value of ‘int system(const char*)’, declared with attribute warn_unused_result
[ 75%] Building CXX object CMakeFiles/yasp_scripted.dir/scriptparser.o
[ 87%] Building CXX object CMakeFiles/yasp_scripted.dir/structs.o
[100%] Building CXX object CMakeFiles/yasp_scripted.dir/iconstack.o
/home/xaghor/Desktop/yasp-scripted-0.99b/iconstack.cpp: In member function ‘virtual void IconStack::mousePressEvent(QGraphicsSceneMouseEvent*)’:
/home/xaghor/Desktop/yasp-scripted-0.99b/iconstack.cpp:64: warning: ignoring return value of ‘int system(const char*)’, declared with attribute warn_unused_result
Linking CXX shared module lib/yasp_scripted.so
[100%] Built target yasp_scripted
Install the project...
-- Install configuration: "release"
-- Installing: /usr/lib/kde4/yasp_scripted.so
-- Set runtime path of "/usr/lib/kde4/yasp_scripted.so" to "/usr/lib"
-- Up-to-date: /usr/share/kde4/services/yasp-scripted.desktop
xaghor@xaghor-kubuntu64:~/Desktop/yasp-scripted-0.99b/build$ kbuildsycoca4
kbuildsycoca4 running...
xaghor@xaghor-kubuntu64:~/Desktop/yasp-scripted-0.99b/build$

I copied the script "systemmonitor.script" to my $HOME/.yasp.script repertory but when I launch the plasmoid nothing happend, I only have a empty applet.....
Do you know why ? I missed anything else ?

Report

patkoscsaba

9 years ago

First of all, good work. I tried YaSP Scripted when it was v0.3 and I did not liked it back then. Now it's much much better and uses less resourses.

I've sent you a mail with my script and screenshot.

And now, what I would like to be implemented in the future:
- icons for meters, charts and text
- I don't know how it is done, but icons should be cached in RAM, so the file is not re-read every time the "value" containing an icon refreshes
- it still uses pretty much resources if charts are updated faster than 4 secs.
- possibility to add value to Title, so I could add, for example, distribution name in the title.
- icons for titles
- I couldn't figure out how to make a font BOLD, it does not accept QFont parameters for bold. Font definition should be like QFont is: QFont ( const QString & family, int pointSize = -1, int weight = -1, bool italic = false )
- you could add "height" parameter for "Meters", too

Report

C

finkandreas

9 years ago

Hello,
probably I wrote it in some comment before, but I'm not using KDE myself at the moment, so it always take a bit longer for the requested updates, but I still work on yasp, if people see bugs, or have feature requests.

some notes from my side to your requests:

- icons for meters, charts and text
meters and charts could get an extra icon, but I do not see why text should get one. Because text with an icon would be the same as value with an icon and key=" ". Just as you did with the top in your script. So you should clarify why text should have an icon...

- I don't know how it is done, but icons should be cached in RAM, so the file is not re-read every time the "value" containing an icon refreshes
The icon is only loaded once during the parsing. Then I have a QPixmap from that icon (probably a shared one, with other instances of KDE). So I do not know, why you think that the icon is reread every time from disk...
Maybe KDE changes the QPixmap (because it is shared) but that has nothing to do with yasp


- it still uses pretty much resources if charts are updated faster than 4 secs.
Yasp is simply using a Plasma::SignalPlotter from the KDE package, so if you want to have it optimized the plotter in KDE itself should be optimized (but that's the job of the KDe guys). But I doubt that the guys from KDE implemented it in a really bad way, so there is probably not much room for optimizations ;)

- possibility to add value to Title, so I could add, for example, distribution name in the title.
- icons for titles
Both things could be done, if I feel like codin' again on yasp scripted...

- I couldn't figure out how to make a font BOLD, it does not accept QFont parameters for bold. Font definition should be like QFont is: QFont ( const QString & family, int pointSize = -1, int weight = -1, bool italic = false )
Nope I'm not going to use this constructor but rather QFont::fromString(), because you can hide everything in one string. For your example you should use sth like that:
Times,12,-1,5,50,0,0,0,0,0
Here the Times is the font family, 12 is the pointSize and 50 stands for a normal font. If you increase it it will become bolder, decrease it and it will be the opposite (values between 0 and 99, as can be seen in the Qt documentation).
As you can see there are even more parameters. If you want to find the line for a specific font configuration write a small program which creates your font, and then use QFont::toString() to see the line you should use... If you don't know how to write the program i could send you the small program by mail.

- you could add "height" parameter for "Meters", too
I have to try whether that works with Plasma::Meter (again something I borrowed from KDE without any adaption)

Report

patkoscsaba

9 years ago

Thanks for the quick reply.

As I said, I don't know how you made the icon thing. I did not check your code. If it's a QPixmap, loaded only once, that's perfect. I just thought to suggest something like this by not knowing the exact procedure you implemented. Yes, I could check the code, but I was too lasy ;)

Why icons for text? Why not, if it's easy to implement.

Thanks for the text type clarification. I always have a hard time figuring out QT documentation ;)

Report

C

finkandreas

9 years ago

Since there is no specific reason for text with icon, I will not implement it (because value with icon is more useful, because both icon and value can have different click events). If I would implement it, I would just duplicate code for no additional advancement.

Thx for the script and screenshot. I've uploaded them in the new version ;)

Report

DuncanKDE

9 years ago

> icons should be cached in RAM,
> so the file is not re-read
> every time the "value" containing
> an icon refreshes

That shouldn't be a problem, given a sane kernel (such as Linux). The system file cache (in RAM) should be enough, as the kernel will automatically take the read request and fill it from cache without ever going to disk, if it's in cache. For something reread every few seconds, it's not going to be dumped from cache, so there should be little issue, regardless of what the app itself does.

Yes, an strace will likely still say it's being opened, read and closed every update, but the disk activity LED shouldn't light up (unless something else is going on), as it'll be loaded from the system file cache.

Still, while I don't do icons here (too much data to display in too little space as it is) and thus I haven't followed what yasp-scripted does with icons, presuming the icon isn't changing, it'd be nice if the icon load could be made single-shot, regardless of what the timeing on widget it's associated with is. No need to be opening, reading and closing the file, plus redrawing the same icon every few seconds. That's a CPU activity sucker, especially since the file-read will require switching to kernel mode, even if it is in cache. (Actually, the same but to a lessor extreme could apply to the value labels, which don't change, just redraw the value data not the label. Maybe yasp-scripted already does this?)

Report

patkoscsaba

9 years ago

First of all, good work. I tried YaSP Scripted when it was v0.3 and I did not liked it back then. Now it's much much better and uses less resourses.

I've sent you a mail with my script and screenshot.

And now, what I would like to be implemented in the future:
- icons for meters, charts and text
- I don't know how it is done, but icons should be cached in RAM, so the file is not re-read every time the "value" containing an icon refreshes
- it still uses pretty much resources if charts are updated faster than 4 secs.
- possibility to add value to Title, so I could add, for example, distribution name in the title.
- icons for titles
- I couldn't figure out how to make a font BOLD, it does not accept QFont parameters for bold. Font definition should be like QFont is: QFont ( const QString & family, int pointSize = -1, int weight = -1, bool italic = false )
- you could add "height" parameter for "Meters", too

Report

nicollivier

9 years ago

Hi, :)

I use it on Mandriva 2010 x86-64.

With the command htop, I see " mem: 805/3878MB", but with plasmoid "05/3878MB". So I don't have the first digit. I'm alone with this pb?!

Nico

Report

C

finkandreas

9 years ago

That's strange. Could you post the sensors and values you're using for getting this line?

Report

nicollivier

9 years ago

Yes that's strange.

On my laptop:
sensor name="RamApplicationMb" type="engine" cmd="systemmonitor:mem/physical/application:value" math="int $0 1024 /"
sensor name="RamTotalMb" type="program" cmd=$cat /proc/meminfo | grep MemTotal | sed -e "s/MemTotal: *\([0-9]*\).*/\1/"$ math="int $0 1024 /" interval="single"
meter use="RamApplicationMb" use="RamTotalMb" label:0="Ram" label:1="$1 sur $2 Mb" alignment:1="right" min="0" max="$2" value="$1"

And on my desktop I have same code, and it's ok.

But my laptop is Acer 1810TZ with 4Go Ram, Mdv 64b
And my desktop Acer M3640 with 2Go Ram, Mdv 32b

Report

C

finkandreas

9 years ago

Another thing you could try: make the plasmoid wider, than the '8' should appear...
If you see the 805 then completely the problem is that svg for the meter defines a too small field, so you can change the svg itself and define a bigger field.
But the simplest is to resize the plasmoid that it becomes wider.

Report

DuncanKDE

9 years ago

... Or try using a smaller or at least narrower font...

Report

nicollivier

9 years ago

I enlarged the size of the window and it's good.

Tks :)

Report

DuncanKDE

9 years ago

Hmm... I don't use meters here, as I like to see the trends and thus use plotters instead. The plotters don't display a number, however, just the plot, so I use a value line as well, thus getting a text readout of the current number as well as a plot over time.

What happens if you add a value line? Does it show the whole thing, or is it truncated as well? Does the meter have enough room to display the whole thing?

Here's a value line to try:

value key="RamApp" use="RamApplicationMb" format="$1 MB"

If that shows up correctly, then the sensor is correct, the number is just being truncated in the meter display. As I don't do meters I can't help much there. If the number is coming up 05 instead of 805 there as well, then perhaps it's a sensor issue, and since the sensor is using the systemmonitor engine, it's likely a bug in it, that is, in kde itself, since that's where the engine is.

FWIW, I'm running Gentoo/amd64 here, so 64-bit, without issues, but as I said I don't do meters only plotters and values, so I'd not have seen any meter issues, and of course if it's a distribution bug, I'd have missed that too since I'm on a different distribution.

Report

8 years ago

1.0.8a - wrong folder prefix ;)

1.0.8 - bug fixed when reparsing (the kde-plasma-handle was deleted, but we should not delete it)

1.0.7 - bug fixed if engine-sensors contains a colon
- Added script by joseph (thx for the script)
- New script by aldo (thx for the script)

1.0.6 - stack keyword added to plotter (thx Chris99 for the patch)
- Script by mtr added (thx for the script)

1.0.5 - fix crash on reparsing in kde-4.5.2 (with 4.5.2 reparsing works again, but 4.5.1 and 4.5.0 have a bug)

1.0.4
- Label preferredSize setting correctly + sizePolicy changed

1.0.3
- meter sizePolicy changed (works now better in KDE-4.5)
- bugfix for KDE-4.5 such that it does not crash on removal

1.0.2
- workaround for problems with KDE-4.5 and meters (min_height parameter added)
- added script by aldo to the package (italian labels)
(- known issue: yasp-scripted crashes on reparsing in kde-4.5. This will be fixed in a later release)

1.0.1 - bug fixed if yasp is closed while parsing the script

1.0: - Reparsing should be more stable

12345678910
123
product-maker domryba Apr 16 2015 9 excellent
product-maker LeifErikson May 29 2013 9 excellent
product-maker XenoPL Nov 01 2012 9 excellent
product-maker Sweyn78 Aug 27 2012 9 excellent
product-maker matafleur Mar 05 2012 9 excellent
product-maker gerstavros Jan 15 2012 9 excellent
product-maker Heart Nov 14 2011 9 excellent
product-maker momonster Jul 02 2011 9 excellent
product-maker superpepo Jun 18 2011 9 excellent
product-maker yield65 May 29 2011 9 excellent
product-maker marcotangaro Mar 24 2011 9 excellent
product-maker theZest Feb 28 2011 9 excellent
product-maker bugmenot1234 Feb 27 2011 9 excellent
product-maker rangerGR Feb 25 2011 9 excellent
product-maker schleby Feb 14 2011 9 excellent
product-maker phiga2 Feb 11 2011 3 bad
product-maker srog Feb 01 2011 9 excellent
product-maker opera1818 Dec 17 2010 9 excellent
product-maker cialdo99 Nov 18 2010 9 excellent
product-maker deabru Nov 07 2010 9 excellent
product-maker schnelle Nov 05 2010 9 excellent
product-maker Vzlom Oct 27 2010 9 excellent
product-maker vatsok Oct 21 2010 9 excellent
product-maker SeaJey Oct 07 2010 9 excellent
product-maker Count: 4 Rating: 5.0

domryba

Apr 16 2015

xrooters

Jul 13 2013

LeifErikson

May 29 2013

XenoPL

Nov 01 2012

despot77

May 28 2012

Fred6681

Jul 02 2011

yield65

May 29 2011

marcotangaro

Mar 24 2011

extra

Nov 09 2010

Contrast

Aug 21 2010

poelzi

Feb 25 2010

hellblade

Feb 16 2010

Franksuse64

Feb 02 2010

DaiVied

Dec 19 2009

nicollivier

Dec 02 2009

Droopy159

Nov 18 2009

SeaJey

Nov 03 2009

Sibob

Nov 03 2009

DuncanKDE

Oct 22 2009

kanutron

Sep 18 2009

t3ddy

Sep 04 2009

Montblanc

Aug 28 2009

NForce

Aug 10 2009

Havoc65

Jul 31 2009
File (click to download) Version Description Downloads Date Filesize DL OCS-Install
Pling
*Needs ocs-url or ocs-store to install things
Details
license
version
1.0.8a
updated Feb 25 2011
added Jul 31 2009
downloads today
0
page views today 6