Yep... At one point the position was working for me too, then it quit for no reason I could see.
Position works because it`s used outside of the gtkDialog3 code " between the main double quotes ".
If like gtkDialog2 it used the full line at the end, then like gtkDialog2 it would work also...
gtkdialog3 -p -geometry ${sizeX}x${sizeY}+${posX}+${posY} --program=DRIVEMAN

I added this line to test if variables were getting into the gtkdialog3 code and they are...
<button><label>Test Path</label><action>echo $appPATH</action></button>

For some reason this gtkDialog3 line won`t use it`s variables:
<window title=\"DM\" default_width=\"sizeX\" default_height=\"sizeY\">

Help Options:
-?, --help Show help options
--help-all Show all help options
--help-gtk Show GTK+ Options

Application Options:
-v, --version Print version information and exit.
-d, --debug Debug mode prints the processed characters.
-p, --program=variable Get the GUI description from the environment.
-g, --glade-xml=filename Get the GUI description from this Glade file.
-f, --file=filename Get the GUI description from a regular file.
-i, --include=filename Include the given file when executing.
-e, --event-driven=filename Execute the file as an event driven program.
-s, --stdin Get the GUI description from standard input.
-w, --no-warning Suppress warning messages.
-G, --geometry=[XxY][+W+H] The placement and the size of the window.
-c, --center Center the windows on the screen.
--print-ir Print the internal representation and exit.
--display=DISPLAY X display to use

So it's either -G XxY+W+H or --geometry=XxY+W+H

Also -p XXX is short for --program=XXX. (you only need one!)

If you want to add command line parameters to the geometry try:

Code:

gtkdialog3 --geometry=${1-+20+30} --program=DRIVEMAN

Then you can call the script as:

Code:

./scriptname 200x400+200+300

Also

Quote:

For some reason this gtkDialog3 line won`t use it`s variables:
<window title=\"DM\" default_width=\"sizeX\" default_height=\"sizeY\">

Thanks potong; The options that I want to know how they work are:
-f, --file=filename Get the GUI description from a regular file.
-e, --event-driven=filename Execute the file as an event driven program.

Back to basics, this code shows that gtkDialog3 also doesn`t need the variables to be exported:

RIGHT=14 DOWN=36 WIDTH=80 HEIGHT=150 # define variables with defaults
DRIVE= # export this variable now so the script can use it after gtkdialog3
# has assigned it a value

#probepart |grep -v none |sed 's#^/dev/##' |sed 's/|.*$//' |sed 's/$/||/' > /tmp/drvinfo # make tablebox input file
# Do we need a temp file?
# Stick it in a function and you can refresh it from the gui.

Very interesting potong, lots of nifty code... You`re right, a file isn`t needed for the Table.
But I can`t figure out what code made the GUI capable of being smaller.
Is it using only the geometry option? Please simplify what made it behave properly.
You`ve changed so much about the way the GUI works, it`s very hard to tell...

Three cheers for potang, I got it sizing the gtkDialog3 GUI to any size in code..!!!
So weird that the GUI only gets bigger and never smaller with the mouse. Serious Bug!
But anyway... If you shutdown the GUI it will come back to the specified size when run again.

I have noticed in a number of gtkdialog3 programs that temporary file(s) are created in /tmp.
The reasoning is that the /tmp directory will be rebuilt when Puppy is next run.
This is true for frugal installs of Puppy.
But with a full install of Puppy, the /tmp directory does not get rebuilt and the temporary files do not get automatically removed on reboot.
So it would be good practice to add lines to the gtkdialog3 script when one creates it to remove those temporary files.

Actually the /tmp dir. use to be in ram only, so it was erased by default upon rebooting.
But now that Puppy unions on "/", the /tmp dir. has to be deleted by code at shutdown.
This means temp. files in /tmp aren`t really temp. at all... They`re written to the Save layer.
This slows the read / write procedure down as accessing /tmp is an access to the HD usually.

potong; Thanks, I got my small test GUI ( like the one you`ve shown above...) working..!
I like your extended strung out sed command, I`ve tried ones like it but have had little luck.
Defining the body of the GUI code differently is interesting also, it has some possibilities.

Three cheers for potang, I got it sizing the gtkDialog3 GUI to any size in code..!!!
So weird that the GUI only gets bigger and never smaller with the mouse. Serious Bug!
But anyway... If you shutdown the GUI it will come back to the specified size when run again.

The thing that bothers me is that there seems to be no consistency in use of code.

For example, Zigbert's example of saving window size and position slightly modified by me, works and will let you resize the window down to it's original size.
But the same code segments placed in your Driveman script will NOT let you shrink the size of the window.

The modified code from Zigbert so you can see what I mean.
Run it once and exit. Then when you run it again, it will show the window with the new size and position. And it WILL let you shrink the window back to its original size!