hellooooooooooooooo Habitual. What didn't you tell me about this directly? And in case people didn't believe you about the number of conkys I'd have to update (when) if I switch to v1.10,
take a look. Interesting to note, those are conky v1.9 and check out my CPU usage in there on Desktop #1 - it's a lie, I have iceweasel and a whole bunch of things running - normally my CPU usage runs
between 1 and 3 percent with just 16 daily conkys running.
Now saying that I wouldn't convert all of them, some are "historical" versions of my old conkys ... like my very first conky from Dec 2007, some are OPC - Other People's Conkys - like Habitual's or 'tweaks' of OPCs that I help them 'debug'. I'm a Conky Museum.
@mzsade - images in conky do have an affect on CPU usage. V1.9 or what ever. But I'm 'guessing' since v1.10 is LUA based it might
not be as resource friendly as the plain old text based conkys.
Here's a test - bit extreme - of two of Teo's weather scripts merged, 2b-wunderground and 4-moon. The original images with the weather script are 250x150 in size. The smaller images are a) resized to "-s 50x30" or b) not resized as I have made the images smaller:
Code:
${image /media/5/Conky/2b_Wunderground_API/h1.png -p 182,32}
The only thing open when these scrots were taken: medit and my 16 conkys that run on various desktops.
Also using "update_interval 1" for this test. Normally I have it at "update_interval 1800" since it's an open, read me, close me conky.
Note CPU Usage on the right...
Using large images, 250x150, resized to "-s 50x30" with images command
Using large images, 250x150, no resizing with image command
using 50x30 images with no resizing <-- EDIT: had wrong link
Again at
@mzsade is the LUA clock an older londonali1010 clock? It's known to have a memory leak and there are versions tweaked by mrpeachy, dk75 and others to clear that up.