The RAM and swap bar graphs are for memory in use. The Kayak sports 1G of RAM. As for the 235MB figure, that's with a crapload of things running, including Firefox 3 with well over a dozen tabs open. And I have yet to use swap space since using Arch. On the same box running Puppy, swap usage, though not frequent, was often enough for me to question the manner in which the kernel was compiled.

Matt's Draft House is nestled in the little village of Inlet, NY, near where I camp every September.

Sleep? What's sleep? I only nap._________________hangout: ##b0rked on irc.freenode.net
diversion:http://alienjeff.net - visit The Fringe
quote: "The foundation of authority is based upon the consent of the people." - Thomas Hooker

Posted: Mon 13 Oct 2008, 16:24 Post subject:
re: Conky transparencySubject description: Another way to get transparency working for Conky in Puppy 4.x

Hi, this is a follow-up to aussierod's great posts regarding transparency for Conky. This post shows another way I have found to deal with the transparency issue, and works well when you change the wallpaper/background a lot. Sorry in advance for the length, I have to talk it out or I doubt it would make sense, as I am not by any stretch a real programmer.

Back in the 3.x versions of puppy, I had read on this forum that the following lines in .xinitrc loaded Conky at startup and allowed transparency:

Code:

qiv -z /root/Choices/ROX-background.jpg
conky -d &

It worked just fine.

When I changed to puppy 4.0, I noticed this no longer worked to achieve transparency. As WolfPup noted in an earlier post on the first page of this topic, qiv is not pre-installed on Puppy 4.x, but can be added via a .pet file.

Quote:

qiv - http://www.linuxpackages.net/pkg_details.php?id=10168

I added qiv, but still didn't get transparency.

I then found that there was a new program in Puppy 4.x for changing the wallpaper/background under Menu>Desktop>Wallpaper setter. After some research I found that changing the wallpaper/background using this program does not affect /root/Choices/ROX-background.jpg as the previous wallpaper/background program had done. Further research found that the Wallpaper setter program writes the current wallpaper/background choice to the file /root/.config/tmp/bg_img.

Using this information, I changed the additional lines in .xinitrc to the following:

Code:

qiv -z -F /root/.config/tmp/bg_img
conky -d &

After adding the two lines to .xinitrc and restarting X (Menu>Shutdown>Restart X server), I had transparency, finally.

The -z in the qiv line above stretches the image on the background. Qiv has the nice -F option that allows it to read file names from text in a file, thereby allowing it to read the current wallpaper/background image choice from the /root/.config/tmp/bg_img file. I was not able to find an equivalent for xli, which meant qiv was necessary to get this solution to work. So I kept the qiv line instead of using xli as is currently suggested towards the beginning of this topic.

If anyone knows how to have xli read text from the file /root/.config/tmp/bg_img, or if I am just totally confusing this, please let me know.

For those who don't know, to add the new lines to .xinitrc, open the program Geany (Menu>Document>Geany text editor), then use Geany to open the file /root/.xinitrc, and add the new lines above the line "#exec $CURRENTWM". Save the changed file as /root/.xinitrc, then restart X. You will have to add the qiv .pet if you have not already done so, this will need to be done before you restart X for the new lines to work properly. Keep in mind that restarting X will close any windows you may have open, so make sure you have saved anything important.

**************************

OK, so I had transparency. But I like to switch between backgrounds a lot, being a shutterbug with lots of pictures and what must be a mild form of background-viewing ADHD. I began to wonder if there was a better way to change the background and keep Conky in step than having to restart X each time. I did some more research on the Wallpaper setter program in Puppy 4.x, and came up with this solution.

The main work for the Wallpaper setter program appears to occur through the file /usr/local/apps/System/Wallpaper/AppRun. In the AppRun file I added three action lines to the "Apply" button for the Wallpaper setter program. The lines basically 1) stop any Conkys currently running, 2) start qiv with the newly chosen wallpaper/background and then 3) restart Conky. The three lines are similar to those posted earlier in this topic for another use under Puppy 3.x, as follows:

The addition of these lines in the AppRun file goes under the actions for the Apply button in the Wallpaper setter program. The place is towards the bottom of the AppRun file directly after the program writes the wallpaper/background selection to /root/.config/tmp/bg_img, as follows:

Before you add these lines, it would be good to backup the file /usr/local apps/System/Wallpaper/Apprun to something like ApprunOriginal just in case anything goes wrong. To add the new lines, open the program Geany (Menu>Document>Geany text editor), then use Geany to open the file /usr/local apps/System/Wallpaper/Apprun. Add the three new lines as shown above, then restart X (Menu>Shutdown>Restart X server).

Once you have restarted X, you should be able to go in to the Wallpaper setter program and change your wallpaper/background as often as desired, and Conky will re-load with the appropriate wallpaper/background in transparent mode each time. Or it should. I hope it does. Let me know if it doesn't. And remember, this should not be necessary unless you are using Puppy 4.x. Oh, and I haven't tried it on anything but 4.0, so bear that in mind. Yeah, backing up your files might not be a bad idea at all.

For all those I have confused terribly, or bored silly, my sincere apologies.

Be patient as it's a bit of trial and error. You can open a console/terminal and use the commands "killall conky" and "conky &" to avoid having to reboot each time you want to test a new/tweaked configuration.Last edited by alienjeff on Sat 18 Oct 2008, 14:42; edited 1 time in total

Hi Jeff, DC. You know Jeff, "carriage returns" - that's a lot more intelligent than what I was going through.

Well, just for fun, this worked for me. My main config file is .conkyrc (set in the upper left) and I made a copy called .conkyrca (set in the bottom left). I then put the following lines in to .xinitrc:

Code:

conky -d
conky -d -c .conkyrca

I restarted x and both Conkys came up.

By the way, everyone should ignore my post from 10/13, I loaded a fresh frugal Puppy 4.10 on my system and found my instructions/assumptions/understanding to have been flawed. Back to the drawing board...

Of course not. Conky writes to the root window, making it, in effect, part of your wallpaper. Any other window you open will, if needed, go right on top of it._________________Registered Linux user #470359

and I was thinking of other things in the other two corners - conky -c config3 works as well

You didn't mention that before, though you could accomplish that without having two instances of Conky running, though it would be tricky to set up._________________hangout: ##b0rked on irc.freenode.net
diversion:http://alienjeff.net - visit The Fringe
quote: "The foundation of authority is based upon the consent of the people." - Thomas Hooker

One advantage of seperate conky windows is they are different sizes and are only as big as required.

Astute observation and excellent point! Thanks._________________hangout: ##b0rked on irc.freenode.net
diversion:http://alienjeff.net - visit The Fringe
quote: "The foundation of authority is based upon the consent of the people." - Thomas Hooker

Looking at http://conky.sourceforge.net, I see that it's possible to show info on what song is currently playing in the media player, but when I tried all I can get is "MPD: 0:00 ".
I notice that it says, "must be enabled at compile." Is it, and if not, how can I, and how hard would it be?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum