I found the solution, I found that the README.syntax says bullshit, you have to pass all the arguments in the script if you want a styled text, example if you want an oblique bolded text, the README says that if you pass in the script ex.; text format="some crap" font="Crappy Sans,7,-1,5,75" should work but not, you need to pass to the script; text format="some crap" font="Crappy Sans,7,-1,5,75,0,0,0,0"; you need to pass all the arguments even if you won't use it in order to have an styled text, otherwise yasp scripted won't recognize nothing if you pass another argument than the size, you need to pass all. Or at least it works this way for me.

Hi, try to type this command: kbuildsycoca4; then try to restart plasma-desktop

Hello! I did that many times, but it doesn't work. Thanks for your answer :).

What I'd do in such a case is find a command line command that reports the info you need, then use it for your sensor instead of the system monitor engine. (I don't really know enough about wireless to be of help with the specific CLI command, unfortunately.) You can then script it to report the desired value if the net is up, or return some reasonable default, say 0, if it's down, or report the error but truncate it (using cut) if it's too long, thus making yasp-scripted too wide when there's an error. I did that for a couple sensors that under some circumstances would report really long errors here. The command line gives you far more control, but OTOH, isn't as efficient as there's quite a bit more overhead to starting a process than there is in simply reporting some number spit out by an existing process, so will use more CPU.

Thank you for your reply, I ended with something like this: sensor name="WLan1Ip" type="program" cmd=%/sbin/ifconfig wlan1 2>/dev/null | grep 'inet addr' | cut -d':' -f 2 | cut -d' ' -f1% sensor name="Wlan1BitRate" type="program" cmd=%/usr/sbin/iwconfig wlan1 2>/dev/null | grep 'Bit' | cut -d'=' -f2 | cut -d' ' -f1-2% sensor name="Wlan1Quality" type="program" cmd=%/usr/sbin/iwconfig wlan1 2>/dev/null | grep 'Link' | cut -d = -f2 | cut -d ' ' -f1% sensor name="Wlan1Essid" type="program" cmd=%/usr/sbin/iwgetid wlan1 |awk -F ":" '{print $2}'% And an interval of "3000". For the speed meter I finally used mrtg as daemon.

The yasp-scripted plasmoid has a minimum size, controlled by the displayed content of the script you set it to run, but no maximum size -- plasma itself controls that. Change what you have the script set to display to change the minimum size. If placed in a panel larger than the minimum size, plasma will expand one plasmoid dimension (vertical in a horizontal panel, horizontal in a vertical panel) to size of the panel, the other will remain at plasmoid minimum. If placed on the desktop, plasma will let you drag it larger than the minimum size, but not smaller. You mention problems getting it to save its size, but saw what size you're talking about. If it's the minimum size, as I said, you control that yourself based on what you have the script setup to display, the font and font size you set, the height of the plotters, etc. The minimum width of the plasmoid is normally the required width of the widest item. As such, I control it here by setting a fixed-width font (this helps in getting things to line up well, too) and adding spaces or abbreviating labels until the longest line is the size I want. (If some lines can be variable, say due to numbers that can be 1-3 digits, I make sure another line is long enough to allow space for the three digits of the variable lines so the size doesn't keep changing on me every time it updates.) The minimum height is simply the set height of every displayed line, text or graphical, of the script. If the size you're setting is larger than the minimum as explained above, then it's not really the plasmoid setting the size, but plasma itself. If there's a problem with that, it'd therefore be a plasma bug, not something the plasmoid itself controls. And to answer your question, no, I'm not having such a problem, but if there were a plasma bug in that regard I'd not notice it because I configure the minimum size via the script and always use that, of course with the exception of the dimension that's always set by the panel size for plasmoids in a panel.

Thank you for you for your comprehensive answers. I am trying to reduce the plasmoids minimum width. I would like the monitor to be a slim coloumn placed at the edge of my screen. I will try to get control over the mimimum width as suggested by adjusting the script. I guess the statusbars that display the network transfer rates force the plasmoid to widen everytime it gets restarted. I will post a how-to if I am successfull Kudos for your work. Enjoy your weekend.

It depends on what you mean by "saving" the plasmoid dimensions. If you place the plasmoid on your desktop and restart KDE, then it is KDE which will save the size. However if you close the plasmoid, and add it again on the desktop, then yasp-scripted will have its minimum size by default. So what exactly do you try to achieve? Over restarts the plasmoid size should not change (and it's KDE's job to ensure this)

> For me, only one of the scripts works That's because the scripts are all example scripts. They aren't really designed to be run as-is, unless you have exactly the same hardware setup as the person who authored the script. The idea is to customize them to your own hardware, partitions, etc. There's typically two ways to get the data from your system into the script to be displayed -- two different types of "sensors" (the third listed in the README.syntax file is simply a math sensor that manipulates data already available from other sensors). The first (second in the readme) type of sensor uses kde's existing plasma:dataengine, most frequently the systemmonitor engine. But what that engine exposes for use depends on what it can find in your system. The second (first in the readme) type of sensor often requires a bit more work, but is *FAR* more flexible, because it simply takes the STDOUT of a (normally CLI mode command or command-pipe, making it available thru the sensor, for display via one of the text or graphic display elements yasp-scripted makes available for use by your yasp-script. Thus, any output you can get to appear either on the command-line or via kde's systemmonitor engine, you can get yasp-scripted to display (obviously assuming generating that output doesn't require interactivity -- that it can be scripted, of course). What this normally involves for lm_sensors output is running the command in the shell to see what the output you're looking for looks like, then piping that result to grep/sed/cut/awk/head/tail/etc to format it the way you need for the yasp-scripted sensor. (Typically, this will involve grepping a specific line of the output, then cutting/seding/grepping that down to just the number, either for formatted text/graphic display directly, or to be plugged into yasp-scripted's math functions to for instance turn KB into MB or GB, or to divide a value by the total possible to get a percentage for graphic.) The shipped scripts do this already, but by definition, they measure statistics on the specific hardware that the author had. You can either modify the examples for your hardware, or you can use them as illustrations when creating your own. In this way, yasp-scripted is very powerful, because it can be made to display whatever stats your system has available, *BUT*, it's also not a simple install and run plasmoid. It's designed for the power user, the user already familiar enough with his system and the command line, to know both what sort of information he wants, and how to use the traditional UNIX tools and shell scripting to get it in the form she wants. People who don't have the required skills will therefore find the this plasmoid pretty much worthless, because they won't know how to get it to display what they want it to display, not even to the point of modifying the existing scripts for their own system.

Thank you very much for the quick and complete response. I'll try to make it work. Thank you.

Sorry, forgot to search on the page.

I think KDE-4.6.2 screwed up something. Watching the sensors with plasmaengineexplorer there is no systemmonitor:partitions/root/usedspace:value. The best you can do: Write a bugreport to KDE (and change your script in the meanwhile to not show used disk space, until it's fixed in kde)