(OLD) (ARCHIVED) Puppy Linux Discussion Forum

[8-bit]

Sorry to say, but evidently when Puppy Licid 520 was made, that file went by the wayside. It just does not exist in Puppy Lucid 520.
It is interesting that it took this long for me to find out.
As a matter of fact, /usr/X11R7/lib does not exist or do any of the contents that would have been in that directory and any subdirectories in it.

[puppyluvr]

Hello,
In 5 series Puppies, and prob `butu...
Try /usr/share/X11/rgb.txt

[8-bit]

Thank you puppyluvr.
The file was just where you said it was.
But that brings me to a question.
Why did the directory structure change in Lucid?
I thought "out-of-the-box" Puppy versions would, or should I say should have the same directory structure as to file placement for the files that come with Puppy.

[disciple]

But if they are built from another distro's packages they would need to use its filesystem layout, to be compatible with it.

[jpeps]

This animated process indicator graphic makes use of the gtkdialog timer feature. Usage:

myfunction() {
gtimer
code .....
kill -9 `ps | grep GTIMER | grep -v grep | awk '{print $1}'`
}

[zigbert]

Make the gui scalable
>> Did you know that it is possible to make gtkdialog windows fully scalable? That means to be able to drag the window corner, and make the gui bigger.
As long as a <tree>, <table>, <list> or <edit> widget is enclosed ONLY by 1 <hbox> OR <vbox>, the widget will remain scalable both horizontally and vertically. Pfind, Pmusic and Pprocess uses various solutions of this.

>> We have of course a trick to scale more complex guis too...
A <hbox> or <vbox> supports the attribute; scrollable, which resets the hbox/vbox definition. You can enclose a widget by 1 <hbox/vbox> inside the scrollable box. The following example explains my words. Remove the scrollable attribute to see how it normally will act.

[2byte]

Hi everyone,

I need some help please. I have tried to solve this for two days and I'm baffled. Using a tip from earlier in this thread this dialog was constructed with comments. Only in bash 4.1, I get this warning
“./Pupsave-backup: line 409: warning: here-document at line 305 delimited by end-of-file (wanted `EOV')”

Anyone have an idea how to eliminate that warning? BTW there is no line 409 in the script, 321 lines total.

[technosaurus]

i notice you are using EOV instead of EOF ... is that because an EOF is in one of your variables?

cat normally outputs until EOF (octal \004 ... it can be forced with echo -e "\004")

[potong]

2byte: "Sometimes it's hard to see the wood for the trees..."

Simplify the code by removing all the flesh and then add it bit by bit back on to the skeleton.

[2byte]

Thanks guys

potong, your links led to the solution.

[zigbert]

Thunor has enlightened us with a huge speed improvement for complex guis. I have updated first post - Speed issues
______________________________________________________________________

>> For an unknown reason, it is much faster to start your gtkdialog-xml-code from a file than from a variable.
gtkdialog --file=filename
gtkdialog --program=variable
The file alternative is highly recommended if your xml-code is getting complex.

[8-bit]

I hope I have it right, but I have written a gtkdialog script that uses a progress bar in its actions. It was written to restore 2byte's backed up pupsave files, but you can use it to copy a file to another destination.
I ran into a problem after uploading it and found that I had not allowed sufficient time for the copy to start and so a check of the destination file size failed and caused errors in the execution of the script.
Anyway, if you want to try it and see how I got a progress bar to work, just get the file from "Additional Software - utilities". It is under the heading of "Restore Pupsave file....".

I did this as a challenge as I had not seen any actual applications that used a progress bar.
The examples to me do not count because they only increment numbers to make the bar advance with no provision as to how one would use it in an application.
If it bombs for you, open the script in a text editor such as geany and increase the sleep value on line 25.

[jpeps]

[seaside]

[8-bit]

UPDATE!
The Restore Pupsave utility I uploaded may not handle just copying a file since it was written to remove the date-time from a backed up pupsave file.
It uses sed to remove the last 19 characters in the filename after the source path is removed.
I wanted to pass that along to all that try to use it to copy files.