Hey Jan, any progress on Tux Paint Config lately? Need any help? :^)
I'm obviously eager to see it move forward. ;^)
Also, one thing I noticed, I see it's generating a "./tuxpaint.conf",
which will of course need to change down the road... See below.
The other thing I notice is it's writing only the 'name' part of the
options to the file, not the 'value'. e.g., it writes "fullscreen"
instead of "fullscreen=yes" (or "fullscreen=no"). :^)
See Tux Paint's README.txt or README.html for the list of config-file options.
(They're pretty much identical to the command-line ones, which it looks
like you were working off of, except they have the "=yes", "=no" or "=VALUE"
at the end, like "printdelay=5")
As for the conf file name, under Linux, BSD, Solaris, etc., the file
Tux Pain looks for[1] is:
~/.tuxpaintrc
Under Windows and BeOS, the file is called:
./tuxpaint.cfg
CURRENTLY, under Mac OS X, it does it the Linux way. I'm hoping this will
change in the next version (Darrell!?).
Thanks!
-bill!
[1] It actually looks for a system-wide file outside of the user's
home directory first, "/etc/tuxpaint/tuxpaint.conf", where the
"/etc/tuxpaint/" is actually defined by "$(CONFDIR)" in Makefile.
Unless "--nosysconfig" is giving on the command-line.
Obviously, "nosysconfig" is _NOT_ an option that can be used
in a config-file. ;^)
[EMAIL PROTECTED] C is like an industrial strength
http://www.newbreedsoftware.com/ nail gun; if wielded improperly,
New Breed Software it can cause untold carnage.
_______________________________________________
Tuxpaint-dev mailing list
[EMAIL PROTECTED]
http://tux4kids.net/mailman/listinfo/tuxpaint-dev
