notgne2/tuxpaint-pencil-sharpener
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Converted Frequently Asked Questions (FAQ) to HTML.

Browse source 
Mentioned Tux Paint Config. tool in FAQ.
This commit is contained in:
William Kendrick 2005-10-09 22:09:25 +00:00
parent 2778173a26
commit 63e9dcb656
3 changed files with 847 additions and 786 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/CHANGES.txt
View file

@ -304,6 +304,10 @@ http://www.newbreedsoftware.com/tuxpaint/
and feature requests to the SourceForge and feature requests to the SourceForge
tracker: http://sourceforge.net/tracker/?group_id=66938 tracker: http://sourceforge.net/tracker/?group_id=66938
* Converted Frequently Asked Questions (FAQ) to HTML.
* Mentioned Tux Paint Config. tool in FAQ.
* New translations: * New translations:
----------------- -----------------
* Albanian translation created. * Albanian translation created.

743
docs/FAQ.txt
View file

@ -1,534 +1,537 @@
FAQ.txt for Tux Paint Tux Paint
version 0.9.15
Frequently Asked Questions
Tux Paint - A simple drawing program for children. Copyright 2002-2005 by Bill Kendrick and others
New Breed Software
Copyright 2005 by Bill Kendrick bill@newbreedsoftware.com
bill@newbreedsoftware.com http://www.newbreedsoftware. com/tuxpaint/
http://www.newbreedsoftware.com/tuxpaint/
September 14, 2002 - January 9, 2005 September 14, 2002 - October 9, 2005
Drawing-related
Frequently Asked Questions: * The Magic "Fill" Tool Looks Bad
---------------------------
Drawing-related
---------------
The Magic "Fill" Tool Looks Bad
-------------------------------
Tux Paint is probably comparing exact pixel colors when filling.
This is faster, but looks worse. Run the command "tuxpaint --version"
from a command line, and you should see, amongst the other output:
"Low Quality Flood Fill enabled".
To change this, you must rebuild Tux Paint from source. Tux Paint is probably comparing exact pixel colors when filling. This
Be sure to remove or comment out any line that says: is faster, but looks worse. Run the command "tuxpaint --version" from
a command line, and you should see, amongst the other output: "Low
Quality Flood Fill enabled".
#define LOW_QUALITY_FLOOD_FILL To change this, you must rebuild Tux Paint from source. Be sure to
remove or comment out any line that says:
in the "tuxpaint.c" file in the "src" directory. #define LOW_QUALITY_FLOOD_FILL
in the "tuxpaint.c" file in the "src" directory.
Stamp outlines are always rectangles * Stamp outlines are always rectangles
------------------------------------
Tux Paint was built with low-quality (but faster) stamp outlines.
Rebuild Tux Paint from source. Be sure to remove or comment out any Tux Paint was built with low-quality (but faster) stamp outlines.
line that says:
#define LOW_QUALITY_STAMP_OUTLINE Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
in the "tuxpaint.c" file in the "src" directory. #define LOW_QUALITY_STAMP_OUTLINE
in the "tuxpaint.c" file in the "src" directory.
The Rubber Stamp tool is greyed out! * The Rubber Stamp tool is greyed out!
------------------------------------
This means that Tux Paint either couldn't find any stamp images,
or was asked not to load them.
If you installed Tux Paint, but did not install the separate, This means that Tux Paint either couldn't find any stamp images, or
optional "Stamps" collection, quit Tux Paint and install it now. was asked not to load them.
It should be available from the same place you got the main
Tux Paint program.
If you don't want to install the default collection of stamps, If you installed Tux Paint, but did not install the separate, optional
you can just create your own. See the README documentation for "Stamps" collection, quit Tux Paint and install it now. It should be
more on creating PNG image files, TXT text description files, available from the same place you got the main Tux Paint program.
WAV sound files, and DAT text data files that make up stamps. (Note: As of version 0.9.14, Tux Paint comes with a small collection
of example stamps.)
Finally, if you install the stamps, and think they should be loading, If you don't want to install the default collection of stamps, you can
check to see that the "nostamps" option isn't being set. just create your own. See the README documentation for more on
(Either via a "--nostamps" option to Tux Paint's command line, or creating PNG image files, TXT text description files, WAV sound files,
"nostamps=yes" in the configuration file.) and DAT text data files that make up stamps.
If so, either change/remove the "nostamps" option, or you can Finally, if you install the stamps, and think they should be loading,
override it with "--stamps" on the command line or check to see that the "nostamps" option isn't being set. (Either via a
"nostamps=no" or "stamps=yes" in a configuration file. "--nostamps" option to Tux Paint's command line, or "nostamps=yes" in
the configuration file.)
If so, either change/remove the "nostamps" option, or you can override
it with "--stamps" on the command line or "nostamps=no" or
"stamps=yes" in a configuration file.
Interface Problems Interface Problems
------------------
Stamp thumbnails in the Stamp Selector look bad
-----------------------------------------------
Tux Paint was probably compiled with the faster, lower quality
thumbnail code enabled. Run the command: "tuxpaint --version" from
a command line. If, amongst the other output, you see the text:
"Low Quality Thumbnails enabled", then this is what's happening.
Rebuild Tux Paint from source. Be sure to remove or comment out any * Stamp thumbnails in the Stamp Selector look bad
line that says:
#define LOW_QUALITY_THUMBNAILS Tux Paint was probably compiled with the faster, lower quality
thumbnail code enabled. Run the command: "tuxpaint --version" from a
command line. If, amongst the other output, you see the text: "Low
Quality Thumbnails enabled", then this is what's happening.
in the "tuxpaint.c" file in the "src" directory. Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
#define LOW_QUALITY_THUMBNAILS
Pictures in the 'Open' dialog look bad in the "tuxpaint.c" file in the "src" directory.
--------------------------------------
"Low Quality Thumbnails" is probably enabled.
See: "Stamp thumbnails in the Stamp Selector look bad", above.
* Pictures in the 'Open' dialog look bad
The color picker buttons are ugly squares, not pretty buttons! "Low Quality Thumbnails" is probably enabled. See: "Stamp thumbnails
-------------------------------------------------------------- in the Stamp Selector look bad", above.
Tux Paint was probably compiled with the nice looking color
selector buttons disabled. Run the command: "tuxpaint --version" from
a command line. If, amongst the other output, you see the text:
"Low Quality Color Selector enabled", then this is what's happening.
Rebuild Tux Paint from source. Be sure to remove or comment out any * The color picker buttons are ugly squares, not pretty buttons!
line that says:
#define LOW_QUALITY_COLOR_SELECTOR Tux Paint was probably compiled with the nice looking color selector
buttons disabled. Run the command: "tuxpaint --version" from a command
line. If, amongst the other output, you see the text: "Low Quality
Color Selector enabled", then this is what's happening.
in the "tuxpaint.c" file in the "src" directory. Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
#define LOW_QUALITY_COLOR_SELECTOR
The Mouse Pointer Leaves Trails! in the "tuxpaint.c" file in the "src" directory.
--------------------------------
In Windows under fullscreen, and in Linux under fullscreen outside of
X-Window, the SDL library has a bug where the mouse pointer can leave
trails of 'garbage' on the screen.
Until there's a fix, either don't use fullscreen, or disable the * All of the text is in uppercase!
fancy mouse pointer shapes using the configuration option:
nofancycursors=yes The "uppercase" option is on.
Or by using this command-line argument: If you're running Tux Paint from a command-line, make sure you're not
giving it an "--uppercase" option.
--nofancycursors If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--uppercase" is listed as a
command-line argument.
If "--uppercase" isn't being sent on the command line, check
Tux Paint's configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "uppercase=yes".
All of the text is in uppercase! Either remove that line, or simply run Tux Paint with the command-line
-------------------------------- argument: "--mixedcase", which will override the uppercase setting.
The "uppercase" option is on.
If you're running Tux Paint from a command-line, make sure you're Or use Tux Paint Config. and make sure "Show Uppercase Text Only"
not giving it an "--uppercase" option. (under "Languages") is not checked.
If you're running Tux Paint by double-clicking an icon, check the * Tux Paint is in a different language!
properties of the icon to see if "--uppercase" is listed as a
command-line argument.
If "--uppercase" isn't being sent on the command line, check Tux Paint's Make sure your locale setting is correct. See "Tux Paint won't switch
configuration file ("~/.tuxpaintrc" under Linux and Unix, to my language", below.
"tuxpaint.cfg" under Windows) for a line reading: "uppercase=yes".
Either remove that line, or simply run Tux Paint with the command-line * Tux Paint won't switch to my language
argument: "--mixedcase", which will override the uppercase setting.
* Linux and Unix users: Make sure the locale is available
Tux Paint is in a weird language! Make sure the locale you want is available. Check your
--------------------------------- "/etc/locale.gen" file. See the README documentation for the
Make sure your locale setting is correct. locales Tux Paint uses (especially when using the "--lang"
See "Tux Paint won't switch to my language", below. option).
Note: Debian users can simply run "dpkg-reconfigure locales" if
the locales are managed by "dpkg."
Tux Paint won't switch to my language * If you're using the "--lang" command-line option
-------------------------------------
Linux and Unix users: Make sure the locale is available
-------------------------------------------------------
Make sure the locale you want is available. Check your
"/etc/locale.gen" file. See README.txt for the locales
Tux Paint uses (especially when using the "--lang" option).
Note: Debian users can simply run "dpkg-reconfigure locales" Try using the "--locale" command-line option, or your
if the locales are managed by dpkg. operating system's locale settings (e.g., the "$LANG"
environment variable), and please e-mail us regarding your
trouble.
If you're using the "--lang" command-line option * If you're using the "--locale" command-line option
------------------------------------------------
Try using the "--locale" command-line option, or your operating system's
locale settings (e.g., the "$LANG" environment variable), and
please e-mail us regarding your trouble.
If you're using the "--locale" command-line option If this doesn't work, please e-mail us regarding your
-------------------------------------------------- trouble.
If this doesn't work, please e-mail us regarding your trouble.
If you're trying to use your Operating System's locale * If you're trying to use your Operating System's locale
------------------------------------------------------
If this doesn't work, please e-mail us regarding your trouble.
Make sure you have the necessary font If this doesn't work, please e-mail us regarding your
------------------------------------- trouble.
Some translations require their own font. Chinese and Korean,
for example, need Chinese and Korean TrueType Fonts installed
and placed in the proper location, respectively.
The appropriate fonts for such locales can be downloaded from the * Make sure you have the necessary font
Tux Paint website:
http://www.newbreedsoftware.com/tuxpaint/download/fonts/ Some translations require their own font. Chinese and
Korean, for example, need Chinese and Korean TrueType Fonts
installed and placed in the proper location, respectively.
The appropriate fonts for such locales can be downloaded
from the Tux Paint website:
Printing http://www.newbreedsoftware.com/tuxpaint/download/fonts/
--------
Tux Paint won't print, gives an error, or prints garbage (Unix/Linux)
---------------------------------------------------------------------
Tux Paint prints by creating a PostScript rendition of the picture
and sending it to an external command. By default, this command is
the "lpr" printing tool.
If that program is not available (for example, you're using CUPS, Printing
the Common Unix Printing System, and do not have "cups-lpr" installed),
you will need to specify an appropriate command using the
"printcommand" option in Tux Paint's configuration file.
(See the OPTIONS documentation.)
Note: Versions of Tux Paint prior to 0.9.15 used a different default * Tux Paint won't print, gives an error, or prints garbage (Unix/Linux)
command for printing, "pngtopnm | pnmtops | lpr", as Tux Paint output
PNG format, rather than PostScript.
If you had changed your "printcommand" option prior to Tux Paint 0.9.15, Tux Paint prints by creating a PostScript rendition of the picture and
you will need to go back and alter it to accept PostScript. sending it to an external command. By default, this command is the
"lpr" printing tool.
If that program is not available (for example, you're using CUPS, the
Common Unix Printing System, and do not have "cups-lpr" installed),
you will need to specify an appropriate command using the
"printcommand" option in Tux Paint's configuration file. (See the
OPTIONS documentation.)
I get the message "You can't print yet!" when I go to print! Note: Versions of Tux Paint prior to 0.9.15 used a different default
------------------------------------------------------------ command for printing, "pngtopnm | pnmtops | lpr", as Tux Paint output
The "print delay" option is on. You can only print once every X seconds. PNG format, rather than PostScript.
If you're running Tux Paint from a command-line, make sure you're If you had changed your "printcommand" option prior to Tux Paint
not giving it a "--printdelay=..." option. 0.9.15, you will need to go back and alter it to accept PostScript.
If you're running Tux Paint by double-clicking an icon, check the * I get the message "You can't print yet!" when I go to print!
properties of the icon to see if "--printdelay=..." is listed as
a command-line argument.
If a "--printdelay=..." option isn't being sent on the command line, The "print delay" option is on. You can only print once every
check Tux Paint's configuration file ("~/.tuxpaintrc" under Linux and X seconds.
Unix, "tuxpaint.cfg" under Windows) for a line reading:
"printdelay=...".
Either remove that line, set the delay value to 0 (no delay), or If you're running Tux Paint from a command-line, make sure you're not
decrease the delay to a value you prefer. (See README.txt). giving it a "--printdelay=..." option.
Or, you can simply run Tux Paint with the command-line argument:
"--printdelay=0", which will override the configuration file's setting,
and allow unlimited printing. (You won't have to wait between prints.)
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--printdelay=..." is listed as a
command-line argument.
I simply can't print! The button is greyed out! If a "--printdelay=..." option isn't being sent on the command line,
------------------------------------------------ check Tux Paint's configuration file ("~/.tuxpaintrc" under Linux and
The "no print" option is on. Unix, "tuxpaint.cfg" under Windows) for a line reading:
"printdelay=...".
If you're running Tux Paint from a command-line, make sure you're Either remove that line, set the delay value to 0 (no delay), or
not giving it a "--noprint" option. decrease the delay to a value you prefer. (See the README
documentation).
If you're running Tux Paint by double-clicking an icon, check the Or, you can simply run Tux Paint with the command-line argument:
properties of the icon to see if "--noprint" is listed as an argument. "--printdelay=0", which will override the configuration file's
setting, and allow unlimited printing. (You won't have to wait between
prints.)
If "--noprint" isn't on the command-line, check Tux Paint's configuration Or use Tux Paint Config. and make sure "Print Delay" (under
file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg" under Windows) "Printing") is set to "0 seconds."
for a line reading: "noprint=yes".
Either remove that line, or simply run Tux Paint with the command-line * I simply can't print! The button is greyed out!
argument: "--print", which will override the configuration file's setting.
The "no print" option is on.
Saving If you're running Tux Paint from a command-line, make sure you're not
------ giving it a "--noprint" option.
Tux Paint always saves over my old picture!
-------------------------------------------
The "save over" option is enabled. (This disables the prompt
that would appear when you click 'Save.')
If you're running Tux Paint from a command-line, make sure you're If you're running Tux Paint by double-clicking an icon, check the
not giving it a "--saveover" option. properties of the icon to see if "--noprint" is listed as an argument.
If you're running Tux Paint by double-clicking an icon, check the If "--noprint" isn't on the command-line, check Tux Paint's
properties of the icon to see if "--saveover" is listed as an argument. configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "noprint=yes".
If "--saveover" isn't on the command-line, check Tux Paint's configuration Either remove that line, or simply run Tux Paint with the command-line
file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg" under Windows) argument: "--print", which will override the configuration file's
for a line reading: "saveover=yes". setting.
Either remove that line, or simply run Tux Paint with the command-line Or use Tux Paint Config. and make sure "Allow Printing" (under
argument: "--saveoverask", which will override the configuration file's "Printing") is checked.
setting.
Also, see "Tux Paint always saves a new picture!", below. Saving
* Tux Paint always saves over my old picture!
Tux Paint always saves a new picture! The "save over" option is enabled. (This disables the prompt that
------------------------------------- would appear when you click 'Save.')
The "never save over" option is enabled. (This disables the prompt
that would appear when you click 'Save.')
If you're running Tux Paint from a command-line, make sure you're If you're running Tux Paint from a command-line, make sure you're not
not giving it a "--saveovernew" option. giving it a "--saveover" option.
If you're running Tux Paint by double-clicking an icon, check the If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--saveovernew" is listed as an argument. properties of the icon to see if "--saveover" is listed as an
argument.
If "--saveovernew" isn't on the command-line, check Tux Paint's If "--saveover" isn't on the command-line, check Tux Paint's
configuration file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg" configuration file ("~/.tuxpaintrc" under Linux and Unix,
under Windows) for a line reading: "saveover=new". "tuxpaint.cfg" under Windows) for a line reading: "saveover=yes".
Either remove that line, or simply run Tux Paint with the command-line Either remove that line, or simply run Tux Paint with the command-line
argument: "--saveoverask", which will override the configuration file's argument: "--saveoverask", which will override the configuration
setting. file's setting.
Also, see "Tux Paint always saves over my old picture!", above. Or use Tux Paint Config. and make sure "Ask Before Overwriting" (under
"Saving") is checked.
Also, see "Tux Paint always saves a new picture!", below.
Audio Problems * Tux Paint always saves a new picture!
--------------
There's no sound!
-----------------
First, check the obvious:
* Are you certain you're using the computer with the sound card? ;^) The "never save over" option is enabled. (This disables the prompt
* Are your speakers connected and turned on? that would appear when you click 'Save.')
* Is the volume turned up on your speakers?
* Is the volume turned up in your Operating System's "mixer?"
* Are any other programs running that use sound? (They may be
'blocking' Tux Paint)
If sound seems to work otherwise (and you're sure no other program is If you're running Tux Paint from a command-line, make sure you're not
"blocking" the sound device), then Tux Paint is either running with giving it a "--saveovernew" option.
a "no sound" option or was compiled with sound support disabled entirely.
To test whether sound support was enabled when Tux Paint was compiled, If you're running Tux Paint by double-clicking an icon, check the
run Tux Paint from a command line, like so: properties of the icon to see if "--saveovernew" is listed as an
argument.
tuxpaint --version If "--saveovernew" isn't on the command-line, check Tux Paint's
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "saveover=new".
If, amongst the other information, you see "Sound disabled", then the Either remove that line, or simply run Tux Paint with the command-line
version of Tux Paint you're running has sound disabled. Recompiled argument: "--saveoverask", which will override the configuration
Tux Paint, and be sure NOT to build the "nosound" target. file's setting.
(i.e., don't run "make nosound") Be sure SDL_mixer library is available!
If Tux Paint wasn't build without sound support, make sure you're Or use Tux Paint Config. and make sure "Ask Before Overwriting" (under
not running Tux Paint with the "--nosound" option as a command-line "Saving") is checked.
argument.
If it's not, then check the configuration file ("~/.tuxpaintrc" under Also, see "Tux Paint always saves over my old picture!", above.
Linux and Unix, and "tuxpaint.cfg" under Windows) for a line reading:
"nosound=yes".
Either remove that line, or simply run Tux Paint with the command-line Audio Problems
argument: "--sound", which will override the configuration file's setting.
* There's no sound!
The sound effects sound strange First, check the obvious:
-------------------------------
This could have to do with how SDL and SDL_mixer were initialized.
(The buffer size chosen.)
Please e-mail us with details about your computer system. * Are you certain you're using the computer with the sound card?
(Operating system and version, sound card, which version of Tux Paint * Are your speakers connected and turned on?
you're running (run "tuxpaint --version" to verify), and so on.) * Is the volume turned up on your speakers?
* Is the volume turned up in your Operating System's "mixer?"
* Are any other programs running that use sound? (They may be
'blocking' Tux Paint)
* (Unix/Linux) Are you using a sound system, such as aRts, ESD or
GStreamer? If so, try setting the "SDL_AUDIODRIVER" environment
variable before running Tux Paint (e.g.,
"export SDL_AUDIODRIVER=arts"). Or, run Tux Paint through the
system's rerouter (e.g., run "artsdsp tuxpaint" or
"esddsp tuxpaint", instead of simply "tuxpaint").
If sound seems to work otherwise (and you're sure no other program is
"blocking" the sound device), then Tux Paint is either running with a
"no sound" option or was compiled with sound support disabled
entirely.
Fullscreen Mode Problems To test whether sound support was enabled when Tux Paint was compiled,
------------------------ run Tux Paint from a command line, like so:
When I run Tux Paint full-screen and ALT-TAB out, the window turns black!
-------------------------------------------------------------------------
This is apparently a bug in the SDL library. Sorry.
tuxpaint --version
When I run Tux Paint full-screen, it has large borders around it If, amongst the other information, you see "Sound disabled", then the
---------------------------------------------------------------- version of Tux Paint you're running has sound disabled. Recompile
Linux users - Your X-Window server is probably not set with the Tux Paint, and be sure NOT to build the "nosound" target. (i.e., don't
ability to switch to the desired resolution: 640 x 480. run "make nosound") Be sure the SDL_mixer library and its development
(This is typically done manually under the XFree86 server by headers are available!
pressing [Ctrl]-[Alt]-[KeyPad Plus] and -[KeyPad Minus].)
For this to work, your monitor must support that resolution, and If Tux Paint wasn't build without sound support, make sure you're not
you need to have it listed in your X server configuration. running Tux Paint with the "--nosound" option as a command-line
argument.
Check the "Display" subsection of the "Screen" section of your If it's not, then check the configuration file ("~/.tuxpaintrc" under
XFree86 configuration file (typically "/etc/X11/XF86Config-4" or Linux and Unix, and "tuxpaint.cfg" under Windows) for a line reading:
"/etc/X11/XF86Config", depending on the version of XFree86 you're "nosound=yes".
using; 3.x or 4.x, respectively).
Add "640x480" to the appropriate "Modes" line. (e.g., in Either remove that line, or simply run Tux Paint with the command-line
the "Display" subsection that contains 16-bit color depth ("Depth 16"), argument: "--sound", which will override the configuration file's
which is what Tux Paint tries to use.) setting.
e.g.: Or use Tux Paint Config. and make sure "Enable Sound Effects" (under
"Video & Sound") is checked.
Modes "1280x1024" "1024x768" "800x600" "640x480" * The sound effects sound strange
Note that some Linux distributions have tools that can make these This could have to do with how SDL and SDL_mixer were initialized.
changes for you. Debian users can run the command (The buffer size chosen.)
"dpkg-reconfigure xserver-xfree86" as root, for example.
Please e-mail us with details about your computer system. (Operating
system and version, sound card, which version of Tux Paint you're
running (run "tuxpaint --version" to verify), and so on.)
Tux Paint keeps running in Full Screen mode - I want it windowed! Fullscreen Mode Problems
-----------------------------------------------------------------
The "fullscreen" option is set.
If you're running Tux Paint from a command-line, make sure you're * When I run Tux Paint full-screen and ALT-TAB out, the window turns
not giving it a "--fullscreen" option. black!
If you're running Tux Paint by double-clicking an icon, check the This is apparently a bug in the SDL library. Sorry.
properties of the icon to see if "--fullscreen" is listed as an argument.
If "--fullscreen" isn't on the command-line, check Tux Paint's * When I run Tux Paint full-screen, it has large borders around it
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "fullscreen=yes".
Either remove that line, or simply run Tux Paint with the command-line Linux users - Your X-Window server is probably not set with the
argument: "--windowed", which will override the configuration file's ability to switch to the desired resolution: 800×600. (or whatever
setting. resolution you have Tux Paint set to run at.) (This is typically done
manually under the X-Window server by pressing [Ctrl]-[Alt]-[KeyPad
Plus] and -[KeyPad Minus].)
For this to work, your monitor must support that resolution, and you
need to have it listed in your X server configuration.
Other Probelms Check the "Display" subsection of the "Screen" section of your XFree86
-------------- or X.org configuration file (typically "/etc/X11/XF86Config-4" or
Tux Paint won't run "/etc/X11/XF86Config", depending on the version of XFree86 you're
------------------- using; 3.x or 4.x, respectively, or "/etc/X11/xorg.conf" for X.org).
If Tux Paint aborts with the message:
"You're already running a copy of Tux Paint!",
this means it has been launched in the last 30 seconds.
A lockfile ("~/.tuxpaint/lockfile.dat" on Linux and Unix, Add "800x600" (or whatever resolution(s) you want) to the appropriate
"userdata\lockfile.dat" on Windows) is used to make sure Tux Paint "Modes" line. (e.g., in the "Display" subsection that contains 24-bit
isn't run too many times at once (e.g., due to a child impatiently color depth ("Depth 24"), which is what Tux Paint tries to use.) e.g.:
clicking its icon more than once).
Even if the lockfile exists, it contains the 'time' Tux Paint was last Modes "1280x1024" "1024x768" "800x600" "640x480"
run. If it's been more than 30 seconds, Tux Paint should run fine,
and simply update the lockfile with the current time.
If multiple users are sharing the directory where this file is stored Note that some Linux distributions have tools that can make these
(e.g., on a shared network drive), then you'll need to disable this changes for you. Debian users can run the command "dpkg-reconfigure
feature. xserver-xfree86" as root, for example.
To disable the lockfile, add the "--nolockfile" argument to Tux Paint's * Tux Paint keeps running in Full Screen mode - I want it windowed!
command-line.
The "fullscreen" option is set.
I can't quit Tux Paint If you're running Tux Paint from a command-line, make sure you're not
---------------------- giving it a "--fullscreen" option.
The "noquit" option is set. This disables the "Quit" button in
Tux Paint's toolbar (greying it out), and prevents Tux Paint from
being quit using the [Escape] key.
If Tux Paint is not in fullscreen mode, simply click the If you're running Tux Paint by double-clicking an icon, check the
window close button on Tux Paint's title bar. properties of the icon to see if "--fullscreen" is listed as an
(i.e., the "(x) at the upper right.) argument.
If Tux Paint is in fullscreen mode, you will need to use the If "--fullscreen" isn't on the command-line, check Tux Paint's
[Shift] + [Control] + [Escape] sequence on the keyboard to configuration file ("~/.tuxpaintrc" under Linux and Unix,
quit Tux Paint. "tuxpaint.cfg" under Windows) for a line reading: "fullscreen=yes".
(Note: with or without "noquit" set, you can always use the Either remove that line, or simply run Tux Paint with the command-line
[Alt] + [F4] combination on your keyboard to quit Tux Paint.) argument: "--windowed", which will override the configuration file's
setting.
Or use Tux Paint Config. and make sure "Fullscreen" (under "Video &
Sound") is not checked.
I don't want "noquit" mode enabled! Other Probelms
-----------------------------------
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--noquit" option.
If you're running Tux Paint by double-clicking an icon, check the * Tux Paint won't run
properties of the icon to see if "--noquit" is listed as an argument.
If "--noquit" isn't on the command-line, check Tux Paint's If Tux Paint aborts with the message: "You're already running a copy
configuration file ("~/.tuxpaintrc" under Linux and Unix, of Tux Paint!", this means it has been launched in the last 30
"tuxpaint.cfg" under Windows) for a line reading: "noquit=yes". seconds. (On Unix/Linux, this message would appear in a terminal
console if you ran Tux Paint from a command-line. On Windows, this
message would appear in a file named "stdout.txt" in the same folder
where TuxPaint.exe resides (e.g., C:\Program Files\TuxPaint).
Either remove that line, or simply run Tux Paint with the command-line A lockfile ("~/.tuxpaint/lockfile.dat" on Linux and Unix,
argument: "--quit", which will override the configuration file's "userdata\lockfile.dat" on Windows) is used to make sure Tux Paint
setting. isn't run too many times at once (e.g., due to a child impatiently
clicking its icon more than once).
Even if the lockfile exists, it contains the 'time' Tux Paint was last
run. If it's been more than 30 seconds, Tux Paint should run fine, and
simply update the lockfile with the current time.
Tux Paint keeps writing weird messages to the screen / to a text file If multiple users are sharing the directory where this file is stored
--------------------------------------------------------------------- (e.g., on a shared network drive), then you'll need to disable this
A few messages are normal, but if Tux Paint is being extremely verbose feature.
(like listing the name of every rubber-stamp image it finds while loading
them), then it was probably compiled with debugging output turned on.
Rebuild Tux Paint from source. Be sure to remove or comment out any To disable the lockfile, add the "--nolockfile" argument to
line that says: Tux Paint's command-line.
#define DEBUG * I can't quit Tux Paint
in the "tuxpaint.c" file in the "src" directory. The "noquit" option is set. This disables the "Quit" button in
Tux Paint's toolbar (greying it out), and prevents Tux Paint from
being quit using the [Escape] key.
If Tux Paint is not in fullscreen mode, simply click the window close
button on Tux Paint's title bar. (i.e., the "(x)" at the upper right.)
Tux Paint is using options I didn't specify! If Tux Paint is in fullscreen mode, you will need to use the [Shift] +
-------------------------------------------- [Control] + [Escape] sequence on the keyboard to quit Tux Paint.
By default, Tux Paint first looks at configuration files for
options.
Unix and Linux (Note: with or without "noquit" set, you can always use the [Alt] +
-------------- [F4] combination on your keyboard to quit Tux Paint.)
Under Unix and Linux, it first examines the system-wide
configuration file, located here:
/etc/tuxpaint/tuxpaint.conf * I don't want "noquit" mode enabled!
It then examines the user's personal configuration file: If you're running Tux Paint from a command-line, make sure you're not
giving it a "--noquit" option.
~/.tuxpaintrc If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--noquit" is listed as an argument.
Finally, any options sent as command-line arguments are used. If "--noquit" isn't on the command-line, check Tux Paint's
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "noquit=yes".
Windows Either remove that line, or simply run Tux Paint with the command-line
------- argument: "--quit", which will override the configuration file's
Under Windows, Tux Paint first examines the configuration file: setting.
tuxpaint.cfg Or use Tux Paint Config. and make sure "Disable Quit Button and
[Escape] Key" (under "Simplification") is not checked.
Then, any options sent as command-line arguments are used. * Tux Paint keeps writing weird messages to the screen / to a text file
A few messages are normal, but if Tux Paint is being extremely verbose
(like listing the name of every rubber-stamp image it finds while
loading them), then it was probably compiled with debugging output
turned on.
This means that if anything is set in a configuration file that Rebuild Tux Paint from source. Be sure to remove or comment out any
you don't want set, you'll need to either change the config. file line that says:
(if you can), or override the option on the command-line.
For example, if "/etc/tuxpaint/tuxpaint.conf" includes an option #define DEBUG
to disable sound:
nosound=yes in the "tuxpaint.c" file in the "src" directory.
You can reenable sound by either adding this option to your own * Tux Paint is using options I didn't specify!
".tuxpainrc" file:
sound=yes By default, Tux Paint first looks at configuration files for options.
Or by using this command-line argument: * Unix and Linux
--sound Under Unix and Linux, it first examines the system-wide
configuration file, located here:
/etc/tuxpaint/tuxpaint.conf
Linux and Unix users can also disable the system-wide configuration It then examines the user's personal configuration file:
file by including the following command-line argument:
--nosysconfig ~/.tuxpaintrc
Tux Paint will then only look at "~/.tuxpaintrc" and command-line Finally, any options sent as command-line arguments are used.
arguments to determine what options should be set.
* Windows
Under Windows, Tux Paint first examines the configuration file:
tuxpaint.cfg
Then, any options sent as command-line arguments are used.
This means that if anything is set in a configuration file that you
don't want set, you'll need to either change the config. file (if you
can), or override the option on the command-line.
For example, if "/etc/tuxpaint/tuxpaint.conf" includes an option to
disable sound:
nosound=yes
You can reenable sound by either adding this option to your own
".tuxpainrc" file:
sound=yes
Or by using this command-line argument:
--sound
Linux and Unix users can also disable the system-wide configuration
file by including the following command-line argument:
--nosysconfig
Tux Paint will then only look at "~/.tuxpaintrc" and command-line
arguments to determine what options should be set.
Help / Contact Help / Contact
--------------
Any questions you don't see answered? Let me know!
bill@newbreedsoftware.com Any questions you don't see answered? Let me know!
Or post to our 'tuxpaint-dev' mailing list: bill@newbreedsoftware.com
http://www.newbreedsoftware.com/tuxpaint/lists/ Or post to our 'tuxpaint-users' mailing list:
http://www.newbreedsoftware.com/tuxpaint/lists/

802
docs/html/FAQ.html
View file

@ -26,530 +26,584 @@ com/tuxpaint/</a></p>
<p>September 14, 2002 - October 9, 2005</p> <p>September 14, 2002 - October 9, 2005</p>
</center> </center>
<pre> <h2>Drawing-related</h2>
Frequently Asked Questions:
---------------------------
Drawing-related
---------------
The Magic "Fill" Tool Looks Bad
-------------------------------
Tux Paint is probably comparing exact pixel colors when filling.
This is faster, but looks worse. Run the command "tuxpaint --version"
from a command line, and you should see, amongst the other output:
"Low Quality Flood Fill enabled".
To change this, you must rebuild Tux Paint from source. <ul>
Be sure to remove or comment out any line that says: <li><em>The Magic "Fill" Tool Looks Bad</em>
<p>Tux&nbsp;Paint is probably comparing exact pixel colors when filling.
This is faster, but looks worse. Run the command "tuxpaint --version"
from a command line, and you should see, amongst the other output:
"Low Quality Flood Fill enabled".</p>
<p>To change this, you must rebuild Tux&nbsp;Paint from source.
Be sure to remove or comment out any line that says:</p>
<blockquote><p><code>
#define LOW_QUALITY_FLOOD_FILL #define LOW_QUALITY_FLOOD_FILL
</code></p></blcokquote>
in the "tuxpaint.c" file in the "src" directory. <p>in the "tuxpaint.c" file in the "src" directory.</p>
</li>
<li><em>Stamp outlines are always rectangles</em>
<p>Tux&nbsp;Paint was built with low-quality (but faster) stamp outlines.</p>
Stamp outlines are always rectangles <p>Rebuild Tux&nbsp;Paint from source. Be sure to remove or comment out any
------------------------------------ line that says:</p>
Tux Paint was built with low-quality (but faster) stamp outlines.
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
<blockquote><p><code>
#define LOW_QUALITY_STAMP_OUTLINE #define LOW_QUALITY_STAMP_OUTLINE
</code></p></blockquote>
in the "tuxpaint.c" file in the "src" directory. <p>in the "tuxpaint.c" file in the "src" directory.</p>
</li>
<li><em>The Rubber Stamp tool is greyed out!</em>
<p>This means that Tux&nbsp;Paint either couldn't find any stamp images,
or was asked not to load them.</p>
The Rubber Stamp tool is greyed out! <p>If you installed Tux&nbsp;Paint, but did not install the separate,
------------------------------------ optional "Stamps" collection, quit Tux&nbsp;Paint and install it now.
This means that Tux Paint either couldn't find any stamp images, It should be available from the same place you got the main
or was asked not to load them. Tux&nbsp;Paint program. <i>(Note: As of version 0.9.14, Tux&nbsp;Paint
comes with a small collection of example stamps.)</i></p>
If you installed Tux Paint, but did not install the separate, <p>If you don't want to install the default collection of stamps,
optional "Stamps" collection, quit Tux Paint and install it now. you can just create your own. See the <a href="README.html">README
It should be available from the same place you got the main documentation</a> for more on creating PNG image files, TXT text
Tux Paint program. description files, WAV sound files, and DAT text data files that
make up stamps.</p>
If you don't want to install the default collection of stamps, <p>Finally, if you install the stamps, and think they should be loading,
you can just create your own. See the README documentation for check to see that the "nostamps" option isn't being set.
more on creating PNG image files, TXT text description files, (Either via a "--nostamps" option to Tux&nbsp;Paint's command line, or
WAV sound files, and DAT text data files that make up stamps. "nostamps=yes" in the configuration file.)</p>
Finally, if you install the stamps, and think they should be loading, <p>If so, either change/remove the "nostamps" option, or you can
check to see that the "nostamps" option isn't being set. override it with "--stamps" on the command line or
(Either via a "--nostamps" option to Tux Paint's command line, or "nostamps=no" or "stamps=yes" in a configuration file.</p>
"nostamps=yes" in the configuration file.) </li>
</ul>
If so, either change/remove the "nostamps" option, or you can <h2>Interface Problems</h2>
override it with "--stamps" on the command line or
"nostamps=no" or "stamps=yes" in a configuration file.
<ul>
<li><em>Stamp thumbnails in the Stamp Selector look bad</em>
<p>Tux&nbsp;Paint was probably compiled with the faster, lower quality
thumbnail code enabled. Run the command: "tuxpaint --version" from
a command line. If, amongst the other output, you see the text:
"Low Quality Thumbnails enabled", then this is what's happening.</p>
Interface Problems <p>Rebuild Tux&nbsp;Paint from source. Be sure to remove or comment out any
------------------ line that says:</p>
Stamp thumbnails in the Stamp Selector look bad
-----------------------------------------------
Tux Paint was probably compiled with the faster, lower quality
thumbnail code enabled. Run the command: "tuxpaint --version" from
a command line. If, amongst the other output, you see the text:
"Low Quality Thumbnails enabled", then this is what's happening.
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
<blockquote><p><code>
#define LOW_QUALITY_THUMBNAILS #define LOW_QUALITY_THUMBNAILS
</code></p></blockquote>
in the "tuxpaint.c" file in the "src" directory. <p>in the "tuxpaint.c" file in the "src" directory.</p>
</li>
<li><em>Pictures in the 'Open' dialog look bad</em>
<p>"Low Quality Thumbnails" is probably enabled.
See: "Stamp thumbnails in the Stamp Selector look bad", above.</p>
</li>
Pictures in the 'Open' dialog look bad <li><em>The color picker buttons are ugly squares, not pretty buttons!</em>
-------------------------------------- <p>Tux&nbsp;Paint was probably compiled with the nice looking color
"Low Quality Thumbnails" is probably enabled. selector buttons disabled. Run the command: "tuxpaint --version" from
See: "Stamp thumbnails in the Stamp Selector look bad", above. a command line. If, amongst the other output, you see the text:
"Low Quality Color Selector enabled", then this is what's happening.</p>
<p>Rebuild Tux&nbsp;Paint from source. Be sure to remove or comment out any
line that says:</p>
The color picker buttons are ugly squares, not pretty buttons! <blockquote><p><code>
--------------------------------------------------------------
Tux Paint was probably compiled with the nice looking color
selector buttons disabled. Run the command: "tuxpaint --version" from
a command line. If, amongst the other output, you see the text:
"Low Quality Color Selector enabled", then this is what's happening.
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
#define LOW_QUALITY_COLOR_SELECTOR #define LOW_QUALITY_COLOR_SELECTOR
</code></p></blockquote>
in the "tuxpaint.c" file in the "src" directory. <p>in the "tuxpaint.c" file in the "src" directory.</p>
</li>
<li><em>All of the text is in uppercase!</em>
<p>The "uppercase" option is on.</p>
The Mouse Pointer Leaves Trails! <p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
-------------------------------- not giving it an "--uppercase" option.</p>
In Windows under fullscreen, and in Linux under fullscreen outside of
X-Window, the SDL library has a bug where the mouse pointer can leave
trails of 'garbage' on the screen.
Until there's a fix, either don't use fullscreen, or disable the <p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
fancy mouse pointer shapes using the configuration option: properties of the icon to see if "--uppercase" is listed as a
command-line argument.</p>
nofancycursors=yes <p>If "--uppercase" isn't being sent on the command line, check
Tux&nbsp;Paint's configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "uppercase=yes".</p>
Or by using this command-line argument: <p>Either remove that line, or simply run Tux&nbsp;Paint with the
command-line argument: "--mixedcase", which will override the uppercase
setting.</p>
--nofancycursors <p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
"Show Uppercase Text Only" (under "Languages") is not checked.</p>
</li>
<li><em>Tux&nbsp;Paint is in a different language!</em>
<p>Make sure your locale setting is correct.
See "Tux&nbsp;Paint won't switch to my language", below.</p>
All of the text is in uppercase! <li><em>Tux&nbsp;Paint won't switch to my language</em>
-------------------------------- <ul>
The "uppercase" option is on. <li><i>Linux and Unix users: Make sure the locale is available</i></li>
<p>Make sure the locale you want is available. Check your
"/etc/locale.gen" file. See the
<a href="README.html">README documentation</a> for the locales
Tux&nbsp;Paint uses (especially when using the "--lang" option).</p>
If you're running Tux Paint from a command-line, make sure you're <p>Note: Debian users can simply run "dpkg-reconfigure locales"
not giving it an "--uppercase" option. if the locales are managed by "dpkg."</p>
If you're running Tux Paint by double-clicking an icon, check the <ul>
properties of the icon to see if "--uppercase" is listed as a <li>If you're using the "--lang" command-line option
command-line argument. <p>Try using the "--locale" command-line option, or your operating
system's locale settings (e.g., the "$LANG" environment variable), and
please e-mail us regarding your trouble.</p>
</li>
If "--uppercase" isn't being sent on the command line, check Tux Paint's <li>If you're using the "--locale" command-line option
configuration file ("~/.tuxpaintrc" under Linux and Unix, <p>If this doesn't work, please e-mail us regarding your trouble.</p>
"tuxpaint.cfg" under Windows) for a line reading: "uppercase=yes". </li>
Either remove that line, or simply run Tux Paint with the command-line <li>If you're trying to use your Operating System's locale
argument: "--mixedcase", which will override the uppercase setting. <p>If this doesn't work, please e-mail us regarding your trouble.</p>
</li>
<li>Make sure you have the necessary font
<p>Some translations require their own font. Chinese and Korean,
for example, need Chinese and Korean TrueType Fonts installed
and placed in the proper location, respectively.</p>
Tux Paint is in a weird language! <p>The appropriate fonts for such locales can be downloaded from the
--------------------------------- Tux&nbsp;Paint website:</p>
Make sure your locale setting is correct.
See "Tux Paint won't switch to my language", below.
<blockquote><p>
<a href="http://www.newbreedsoftware.com/tuxpaint/download/fonts/"
>http://www.newbreedsoftware.com/tuxpaint/download/fonts/</a>
</p></blockquote>
</li>
</ul>
</li>
</ul>
</li>
</ul>
Tux Paint won't switch to my language <h2>Printing</h2>
------------------------------------- <ul>
Linux and Unix users: Make sure the locale is available <li><em>Tux&nbsp;Paint won't print, gives an error, or prints garbage
------------------------------------------------------- (Unix/Linux)</em>
Make sure the locale you want is available. Check your <p>Tux&nbsp;Paint prints by creating a PostScript rendition of the picture
"/etc/locale.gen" file. See README.txt for the locales and sending it to an external command. By default, this command is
Tux Paint uses (especially when using the "--lang" option). the "lpr" printing tool.</p>
Note: Debian users can simply run "dpkg-reconfigure locales" <p>If that program is not available (for example, you're using CUPS,
if the locales are managed by dpkg. the Common Unix Printing System, and do not have "cups-lpr" installed),
you will need to specify an appropriate command using the
"printcommand" option in Tux&nbsp;Paint's configuration file.
(See the <a href="OPTIONS.html">OPTIONS documentation</a>.)</p>
If you're using the "--lang" command-line option <p><i>Note: Versions of Tux&nbsp;Paint prior to 0.9.15 used a different
------------------------------------------------ default command for printing, "pngtopnm&nbsp;|&nbsp;pnmtops&nbsp;|&nbsp;lpr",
Try using the "--locale" command-line option, or your operating system's as Tux&nbsp;Paint output PNG format, rather than PostScript.</p>
locale settings (e.g., the "$LANG" environment variable), and
please e-mail us regarding your trouble.
If you're using the "--locale" command-line option <p>If you had changed your "printcommand" option prior to Tux&nbsp;Paint
-------------------------------------------------- 0.9.15, you will need to go back and alter it to accept PostScript.</p>
If this doesn't work, please e-mail us regarding your trouble. </li>
If you're trying to use your Operating System's locale <li><em>I get the message "You can't print yet!" when I go to print!</em>
------------------------------------------------------ <p>The "print delay" option is on. You can only print once every
If this doesn't work, please e-mail us regarding your trouble. <i>X</i>&nbsp;seconds.</p>
Make sure you have the necessary font <p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
------------------------------------- not giving it a "--printdelay=..." option.</p>
Some translations require their own font. Chinese and Korean,
for example, need Chinese and Korean TrueType Fonts installed
and placed in the proper location, respectively.
The appropriate fonts for such locales can be downloaded from the <p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
Tux Paint website: properties of the icon to see if "--printdelay=..." is listed as
a command-line argument.</p>
http://www.newbreedsoftware.com/tuxpaint/download/fonts/ <p>If a "--printdelay=..." option isn't being sent on the command line,
check Tux&nbsp;Paint's configuration file ("~/.tuxpaintrc" under Linux and
Unix, "tuxpaint.cfg" under Windows) for a line reading:
"printdelay=...".</p>
<p>Either remove that line, set the delay value to 0 (no delay), or
decrease the delay to a value you prefer. (See the
<a href="README.html">README documentation</a>).</p>
Printing <p>Or, you can simply run Tux&nbsp;Paint with the command-line argument:
-------- "--printdelay=0", which will override the configuration file's setting,
Tux Paint won't print, gives an error, or prints garbage (Unix/Linux) and allow unlimited printing. (You won't have to wait between prints.)</p>
---------------------------------------------------------------------
Tux Paint prints by creating a PostScript rendition of the picture
and sending it to an external command. By default, this command is
the "lpr" printing tool.
If that program is not available (for example, you're using CUPS, <p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
the Common Unix Printing System, and do not have "cups-lpr" installed), "Print Delay" (under "Printing") is set to "0&nbsp;seconds."</p>
you will need to specify an appropriate command using the </li>
"printcommand" option in Tux Paint's configuration file.
(See the OPTIONS documentation.)
Note: Versions of Tux Paint prior to 0.9.15 used a different default <li><em>I simply can't print! The button is greyed out!</em>
command for printing, "pngtopnm | pnmtops | lpr", as Tux Paint output <p>The "no print" option is on.</p>
PNG format, rather than PostScript.
If you had changed your "printcommand" option prior to Tux Paint 0.9.15, <p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
you will need to go back and alter it to accept PostScript. not giving it a "--noprint" option.</p>
<p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
properties of the icon to see if "--noprint" is listed as an argument.</p>
I get the message "You can't print yet!" when I go to print! <p>If "--noprint" isn't on the command-line, check Tux&nbsp;Paint's
------------------------------------------------------------ configuration file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg"
The "print delay" option is on. You can only print once every X seconds. under Windows) for a line reading: "noprint=yes".</p>
If you're running Tux Paint from a command-line, make sure you're <p>Either remove that line, or simply run Tux&nbsp;Paint with the
not giving it a "--printdelay=..." option. command-line argument: "--print", which will override the configuration
file's setting.</p>
If you're running Tux Paint by double-clicking an icon, check the <p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
properties of the icon to see if "--printdelay=..." is listed as "Allow Printing" (under "Printing") is checked.</p>
a command-line argument. </li>
</ul>
If a "--printdelay=..." option isn't being sent on the command line, <h2>Saving</h2>
check Tux Paint's configuration file ("~/.tuxpaintrc" under Linux and <ul>
Unix, "tuxpaint.cfg" under Windows) for a line reading: <li><em>Tux&nbsp;Paint always saves over my old picture!</em>
"printdelay=...". <p>The "save over" option is enabled. (This disables the prompt
that would appear when you click 'Save.')</p>
Either remove that line, set the delay value to 0 (no delay), or <p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
decrease the delay to a value you prefer. (See README.txt). not giving it a "--saveover" option.</p>
Or, you can simply run Tux Paint with the command-line argument:
"--printdelay=0", which will override the configuration file's setting,
and allow unlimited printing. (You won't have to wait between prints.)
<p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
properties of the icon to see if "--saveover" is listed as an argument.</p>
I simply can't print! The button is greyed out! <p>If "--saveover" isn't on the command-line, check Tux&nbsp;Paint's
------------------------------------------------ configuration file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg"
The "no print" option is on. under Windows) for a line reading: "saveover=yes".</p>
If you're running Tux Paint from a command-line, make sure you're <p>Either remove that line, or simply run Tux&nbsp;Paint with the
not giving it a "--noprint" option. command-line argument: "--saveoverask", which will override the
configuration file's setting.</p>
If you're running Tux Paint by double-clicking an icon, check the <p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
properties of the icon to see if "--noprint" is listed as an argument. "Ask Before Overwriting" (under "Saving") is checked.</p>
If "--noprint" isn't on the command-line, check Tux Paint's configuration <p>Also, see "Tux&nbsp;Paint always saves a new picture!", below.</p>
file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg" under Windows) </li>
for a line reading: "noprint=yes".
Either remove that line, or simply run Tux Paint with the command-line <li><em>Tux&nbsp;Paint always saves a new picture!</em>
argument: "--print", which will override the configuration file's setting. <p>The "never save over" option is enabled. (This disables the prompt
that would appear when you click 'Save.')</p>
<p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
not giving it a "--saveovernew" option.</p>
Saving <p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
------ properties of the icon to see if "--saveovernew" is listed as an
Tux Paint always saves over my old picture! argument.</p>
-------------------------------------------
The "save over" option is enabled. (This disables the prompt
that would appear when you click 'Save.')
If you're running Tux Paint from a command-line, make sure you're <p>If "--saveovernew" isn't on the command-line, check Tux&nbsp;Paint's
not giving it a "--saveover" option. configuration file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg"
under Windows) for a line reading: "saveover=new".</p>
If you're running Tux Paint by double-clicking an icon, check the <p>Either remove that line, or simply run Tux&nbsp;Paint with the
properties of the icon to see if "--saveover" is listed as an argument. command-line argument: "--saveoverask", which will override the
configuration file's setting.</p>
If "--saveover" isn't on the command-line, check Tux Paint's configuration <p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg" under Windows) "Ask Before Overwriting" (under "Saving") is checked.</p>
for a line reading: "saveover=yes".
Either remove that line, or simply run Tux Paint with the command-line <p>Also, see "Tux&nbsp;Paint always saves over my old picture!", above.</p>
argument: "--saveoverask", which will override the configuration file's </li>
setting. </ul>
Also, see "Tux Paint always saves a new picture!", below. <h2>Audio Problems</h2>
<ul>
<li><em>There's no sound!</em>
<p>First, check the obvious:</p>
<ul>
<li>Are you certain you're using the computer with the sound card?
<li>Are your speakers connected and turned on?
<li>Is the volume turned up on your speakers?
<li>Is the volume turned up in your Operating System's "mixer?"
<li>Are any other programs running that use sound? (They may be
'blocking' Tux&nbsp;Paint)
<li>(Unix/Linux) Are you using a sound system, such as aRts, ESD or
GStreamer? If so, try setting the "SDL_AUDIODRIVER" environment variable
before running Tux&nbsp;Paint (e.g., "export&nbsp;SDL_AUDIODRIVER=arts").
Or, run Tux&nbsp;Paint through the system's rerouter (e.g.,
run "artsdsp&nbsp;tuxpaint" or "esddsp&nbsp;tuxpaint", instead of
simply "tuxpaint").
</ul>
Tux Paint always saves a new picture! <p>If sound seems to work otherwise (and you're sure no other program is
------------------------------------- "blocking" the sound device), then Tux&nbsp;Paint is either running with
The "never save over" option is enabled. (This disables the prompt a "no sound" option or was compiled with sound support disabled entirely.</p>
that would appear when you click 'Save.')
If you're running Tux Paint from a command-line, make sure you're <p>To test whether sound support was enabled when Tux&nbsp;Paint was
not giving it a "--saveovernew" option. compiled, run Tux&nbsp;Paint from a command line, like so:</p>
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--saveovernew" is listed as an argument.
If "--saveovernew" isn't on the command-line, check Tux Paint's
configuration file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg"
under Windows) for a line reading: "saveover=new".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--saveoverask", which will override the configuration file's
setting.
Also, see "Tux Paint always saves over my old picture!", above.
Audio Problems
--------------
There's no sound!
-----------------
First, check the obvious:
* Are you certain you're using the computer with the sound card? ;^)
* Are your speakers connected and turned on?
* Is the volume turned up on your speakers?
* Is the volume turned up in your Operating System's "mixer?"
* Are any other programs running that use sound? (They may be
'blocking' Tux Paint)
If sound seems to work otherwise (and you're sure no other program is
"blocking" the sound device), then Tux Paint is either running with
a "no sound" option or was compiled with sound support disabled entirely.
To test whether sound support was enabled when Tux Paint was compiled,
run Tux Paint from a command line, like so:
<blockquote><p><code>
tuxpaint --version tuxpaint --version
</code></p></blockquote>
If, amongst the other information, you see "Sound disabled", then the <p>If, amongst the other information, you see "Sound disabled", then the
version of Tux Paint you're running has sound disabled. Recompiled version of Tux&nbsp;Paint you're running has sound disabled. Recompile
Tux Paint, and be sure NOT to build the "nosound" target. Tux&nbsp;Paint, and be sure NOT to build the "nosound" target.
(i.e., don't run "make nosound") Be sure SDL_mixer library is available! (i.e., don't run "make nosound") Be sure the SDL_mixer library and
its development headers are available!</p>
If Tux Paint wasn't build without sound support, make sure you're <p>If Tux&nbsp;Paint wasn't build without sound support, make sure you're
not running Tux Paint with the "--nosound" option as a command-line not running Tux&nbsp;Paint with the "--nosound" option as a command-line
argument. argument.</p>
If it's not, then check the configuration file ("~/.tuxpaintrc" under <p>If it's not, then check the configuration file ("~/.tuxpaintrc" under
Linux and Unix, and "tuxpaint.cfg" under Windows) for a line reading: Linux and Unix, and "tuxpaint.cfg" under Windows) for a line reading:
"nosound=yes". "nosound=yes".</p>
Either remove that line, or simply run Tux Paint with the command-line <p>Either remove that line, or simply run Tux&nbsp;Paint with the
argument: "--sound", which will override the configuration file's setting. command-line argument: "--sound", which will override the configuration
file's setting.</p>
<p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
"Enable Sound Effects" (under "Video &amp; Sound") is checked.</p>
The sound effects sound strange <li><em>The sound effects sound strange</em>
------------------------------- <p>This could have to do with how SDL and SDL_mixer were initialized.
This could have to do with how SDL and SDL_mixer were initialized. (The buffer size chosen.)</p>
(The buffer size chosen.)
Please e-mail us with details about your computer system. <p>Please e-mail us with details about your computer system.
(Operating system and version, sound card, which version of Tux Paint (Operating system and version, sound card, which version of Tux&nbsp;Paint
you're running (run "tuxpaint --version" to verify), and so on.) you're running (run "tuxpaint --version" to verify), and so on.)</p>
</li>
</ul>
<h2>Fullscreen Mode Problems</h2>
<ul>
<li><em>When I run Tux&nbsp;Paint full-screen and ALT-TAB out, the window turns
black!</em>
Fullscreen Mode Problems <p>This is apparently a bug in the SDL library. Sorry.</p>
------------------------
When I run Tux Paint full-screen and ALT-TAB out, the window turns black!
-------------------------------------------------------------------------
This is apparently a bug in the SDL library. Sorry.
<li><em>When I run Tux&nbsp;Paint full-screen, it has large borders around
it</em>
When I run Tux Paint full-screen, it has large borders around it <p>Linux users - Your X-Window server is probably not set with the
---------------------------------------------------------------- ability to switch to the desired resolution: 800&times;600.
Linux users - Your X-Window server is probably not set with the (or whatever resolution you have Tux&nbsp;Paint set to run at.)
ability to switch to the desired resolution: 640 x 480. (This is typically done manually under the X-Window server by
(This is typically done manually under the XFree86 server by pressing [Ctrl]-[Alt]-[KeyPad Plus] and -[KeyPad Minus].)</p>
pressing [Ctrl]-[Alt]-[KeyPad Plus] and -[KeyPad Minus].)
For this to work, your monitor must support that resolution, and <p>For this to work, your monitor must support that resolution, and
you need to have it listed in your X server configuration. you need to have it listed in your X server configuration.</p>
Check the "Display" subsection of the "Screen" section of your <p>Check the "Display" subsection of the "Screen" section of your
XFree86 configuration file (typically "/etc/X11/XF86Config-4" or XFree86 or X.org configuration file (typically "/etc/X11/XF86Config-4" or
"/etc/X11/XF86Config", depending on the version of XFree86 you're "/etc/X11/XF86Config", depending on the version of XFree86 you're
using; 3.x or 4.x, respectively). using; 3.x or 4.x, respectively, or "/etc/X11/xorg.conf" for X.org).</p>
Add "640x480" to the appropriate "Modes" line. (e.g., in <p>Add "800x600" (or whatever resolution(s) you want) to the appropriate
the "Display" subsection that contains 16-bit color depth ("Depth 16"), "Modes" line. (e.g., in the "Display" subsection that contains 24-bit color
which is what Tux Paint tries to use.) depth ("Depth&nbsp;24"), which is what Tux&nbsp;Paint tries to use.)
e.g.:<p>
e.g.:
<blockquote><p><code>
Modes "1280x1024" "1024x768" "800x600" "640x480" Modes "1280x1024" "1024x768" "800x600" "640x480"
</code></p></blockquote>
Note that some Linux distributions have tools that can make these <p>Note that some Linux distributions have tools that can make these
changes for you. Debian users can run the command changes for you. Debian users can run the command
"dpkg-reconfigure xserver-xfree86" as root, for example. "dpkg-reconfigure xserver-xfree86" as root, for example.</p>
</li>
<li><em>Tux&nbsp;Paint keeps running in Full Screen mode - I want it
windowed!</em>
<p>The "fullscreen" option is set.</p>
Tux Paint keeps running in Full Screen mode - I want it windowed! <p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
----------------------------------------------------------------- not giving it a "--fullscreen" option.</p>
The "fullscreen" option is set.
If you're running Tux Paint from a command-line, make sure you're <p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
not giving it a "--fullscreen" option. properties of the icon to see if "--fullscreen" is listed as an argument.</p>
If you're running Tux Paint by double-clicking an icon, check the <p>If "--fullscreen" isn't on the command-line, check Tux&nbsp;Paint's
properties of the icon to see if "--fullscreen" is listed as an argument. configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "fullscreen=yes".</p>
If "--fullscreen" isn't on the command-line, check Tux Paint's <p>Either remove that line, or simply run Tux&nbsp;Paint with the
configuration file ("~/.tuxpaintrc" under Linux and Unix, command-line argument: "--windowed", which will override the configuration
"tuxpaint.cfg" under Windows) for a line reading: "fullscreen=yes". file's setting.</p>
Either remove that line, or simply run Tux Paint with the command-line <p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
argument: "--windowed", which will override the configuration file's "Fullscreen" (under "Video &amp; Sound") is not checked.</p>
setting. </li>
</ul>
<h2>Other Probelms</h2>
<ul>
<li><em>Tux&nbsp;Paint won't run</em>
<p>If Tux&nbsp;Paint aborts with the message:
"You're already running a copy of Tux&nbsp;Paint!",
this means it has been launched in the last 30 seconds.
(On Unix/Linux, this message would appear in a terminal console if you
ran Tux&nbsp;Paint from a command-line. On Windows, this message would
appear in a file named "stdout.txt" in the same folder where TuxPaint.exe
resides (e.g., C:\Program&nbsp;Files\TuxPaint).</p>
Other Probelms <p>A lockfile ("~/.tuxpaint/lockfile.dat" on Linux and Unix,
-------------- "userdata\lockfile.dat" on Windows) is used to make sure Tux&nbsp;Paint
Tux Paint won't run isn't run too many times at once (e.g., due to a child impatiently
------------------- clicking its icon more than once).</p>
If Tux Paint aborts with the message:
"You're already running a copy of Tux Paint!",
this means it has been launched in the last 30 seconds.
A lockfile ("~/.tuxpaint/lockfile.dat" on Linux and Unix, <p>Even if the lockfile exists, it contains the 'time' Tux&nbsp;Paint was
"userdata\lockfile.dat" on Windows) is used to make sure Tux Paint last run. If it's been more than 30 seconds, Tux&nbsp;Paint should run fine,
isn't run too many times at once (e.g., due to a child impatiently and simply update the lockfile with the current time.</p>
clicking its icon more than once).
Even if the lockfile exists, it contains the 'time' Tux Paint was last <p>If multiple users are sharing the directory where this file is stored
run. If it's been more than 30 seconds, Tux Paint should run fine, (e.g., on a shared network drive), then you'll need to disable this
and simply update the lockfile with the current time. feature.</p>
If multiple users are sharing the directory where this file is stored <p>To disable the lockfile, add the "--nolockfile" argument to
(e.g., on a shared network drive), then you'll need to disable this Tux&nbsp;Paint's command-line.</p>
feature. </li>
To disable the lockfile, add the "--nolockfile" argument to Tux Paint's <li><em>I can't quit Tux&nbsp;Paint</em>
command-line. <p>The "noquit" option is set. This disables the "Quit" button in
Tux&nbsp;Paint's toolbar (greying it out), and prevents Tux&nbsp;Paint from
being quit using the [Escape] key.</p>
<p>If Tux&nbsp;Paint is not in fullscreen mode, simply click the
window close button on Tux&nbsp;Paint's title bar.
(i.e., the "(x)" at the upper right.)</p>
I can't quit Tux Paint <p>If Tux&nbsp;Paint is in fullscreen mode, you will need to use the
---------------------- [Shift] + [Control] + [Escape] sequence on the keyboard to
The "noquit" option is set. This disables the "Quit" button in quit Tux&nbsp;Paint.</p>
Tux Paint's toolbar (greying it out), and prevents Tux Paint from
being quit using the [Escape] key.
If Tux Paint is not in fullscreen mode, simply click the <p>(Note: with or without "noquit" set, you can always use the
window close button on Tux Paint's title bar. [Alt] + [F4] combination on your keyboard to quit Tux&nbsp;Paint.)</p>
(i.e., the "(x) at the upper right.) </li>
If Tux Paint is in fullscreen mode, you will need to use the <li><em>I don't want "noquit" mode enabled!</em>
[Shift] + [Control] + [Escape] sequence on the keyboard to <p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
quit Tux Paint. not giving it a "--noquit" option.</p>
(Note: with or without "noquit" set, you can always use the <p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
[Alt] + [F4] combination on your keyboard to quit Tux Paint.) properties of the icon to see if "--noquit" is listed as an argument.</p>
<p>If "--noquit" isn't on the command-line, check Tux&nbsp;Paint's
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "noquit=yes".</p>
I don't want "noquit" mode enabled! <p>Either remove that line, or simply run Tux&nbsp;Paint with the
----------------------------------- command-line argument: "--quit", which will override the configuration file's
If you're running Tux Paint from a command-line, make sure you're setting.</p>
not giving it a "--noquit" option.
If you're running Tux Paint by double-clicking an icon, check the <p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
properties of the icon to see if "--noquit" is listed as an argument. "Disable Quit Button and [Escape] Key" (under "Simplification")
is not checked.</p>
</li>
If "--noquit" isn't on the command-line, check Tux Paint's <li><em>Tux&nbsp;Paint keeps writing weird messages to the screen / to a text
configuration file ("~/.tuxpaintrc" under Linux and Unix, file</em>
"tuxpaint.cfg" under Windows) for a line reading: "noquit=yes". <p>A few messages are normal, but if Tux&nbsp;Paint is being extremely
verbose (like listing the name of every rubber-stamp image it finds while
loading them), then it was probably compiled with debugging output turned
on.</p>
Either remove that line, or simply run Tux Paint with the command-line <p>Rebuild Tux&nbsp;Paint from source. Be sure to remove or comment out any
argument: "--quit", which will override the configuration file's line that says:</p>
setting.
Tux Paint keeps writing weird messages to the screen / to a text file
---------------------------------------------------------------------
A few messages are normal, but if Tux Paint is being extremely verbose
(like listing the name of every rubber-stamp image it finds while loading
them), then it was probably compiled with debugging output turned on.
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
<blockquote><p><code>
#define DEBUG #define DEBUG
</code></p></blockquote>
in the "tuxpaint.c" file in the "src" directory. <p>in the "tuxpaint.c" file in the "src" directory.</p>
</li>
<li><em>Tux&nbsp;Paint is using options I didn't specify!</em>
<p>By default, Tux&nbsp;Paint first looks at configuration files for
options.</p>
Tux Paint is using options I didn't specify! <ul>
-------------------------------------------- <li><i>Unix and Linux</i>
By default, Tux Paint first looks at configuration files for <p>Under Unix and Linux, it first examines the system-wide
options. configuration file, located here:</p>
Unix and Linux
--------------
Under Unix and Linux, it first examines the system-wide
configuration file, located here:
<blockquote><p><code>
/etc/tuxpaint/tuxpaint.conf /etc/tuxpaint/tuxpaint.conf
</code></p></blockquote>
It then examines the user's personal configuration file: <p>It then examines the user's personal configuration file:</p>
<blockquote><p><code>
~/.tuxpaintrc ~/.tuxpaintrc
</code></p></blockquote>
Finally, any options sent as command-line arguments are used. <p>Finally, any options sent as command-line arguments are used.</p>
</li>
Windows <li><i>Windows</i>
------- <p>Under Windows, Tux&nbsp;Paint first examines the configuration file:</p>
Under Windows, Tux Paint first examines the configuration file:
<blockquote><p><code>
tuxpaint.cfg tuxpaint.cfg
</blockquote></p></code>
Then, any options sent as command-line arguments are used. <p>Then, any options sent as command-line arguments are used.</p>
</li>
</ul>
<p>This means that if anything is set in a configuration file that
you don't want set, you'll need to either change the config. file
(if you can), or override the option on the command-line.</p>
This means that if anything is set in a configuration file that <p>For example, if "/etc/tuxpaint/tuxpaint.conf" includes an option
you don't want set, you'll need to either change the config. file to disable sound:</p>
(if you can), or override the option on the command-line.
For example, if "/etc/tuxpaint/tuxpaint.conf" includes an option
to disable sound:
<blockquote><p><code>
nosound=yes nosound=yes
</blockquote></p></code>
You can reenable sound by either adding this option to your own <p>You can reenable sound by either adding this option to your own
".tuxpainrc" file: ".tuxpainrc" file:</p>
<blockquote><p><code>
sound=yes sound=yes
</blockquote></p></code>
Or by using this command-line argument: <p>Or by using this command-line argument:</p>
<blockquote><p><code>
--sound --sound
</blockquote></p></code>
<p>Linux and Unix users can also disable the system-wide configuration
file by including the following command-line argument:</p>
Linux and Unix users can also disable the system-wide configuration <blockquote><p><code>
file by including the following command-line argument:
--nosysconfig --nosysconfig
</blockquote></p></code>
Tux Paint will then only look at "~/.tuxpaintrc" and command-line <p>Tux&nbsp;Paint will then only look at "~/.tuxpaintrc" and command-line
arguments to determine what options should be set. arguments to determine what options should be set.</p>
</li>
</ul>
<h2>Help / Contact</h2>
<p>Any questions you don't see answered? Let me know!</p>
Help / Contact <blockquote><p><a href="mailto:bill@newbreedsoftware.com"
-------------- >bill@newbreedsoftware.com</a></p></blockquote>
Any questions you don't see answered? Let me know!
bill@newbreedsoftware.com <p>Or post to our 'tuxpaint-users' mailing list:</p>
Or post to our 'tuxpaint-dev' mailing list: <blockquote><p><a href="http://www.newbreedsoftware.com/tuxpaint/lists/"
>http://www.newbreedsoftware.com/tuxpaint/lists/</a></p></blockquote>
http://www.newbreedsoftware.com/tuxpaint/lists/
</pre>
</body></html> </body></html>