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
tracker: http://sourceforge.net/tracker/?group_id=66938
* Converted Frequently Asked Questions (FAQ) to HTML.
* Mentioned Tux Paint Config. tool in FAQ.
* New translations:
-----------------
* 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
http://www.newbreedsoftware.com/tuxpaint/
bill@newbreedsoftware.com
http://www.newbreedsoftware. com/tuxpaint/
September 14, 2002 - January 9, 2005
September 14, 2002 - October 9, 2005
Drawing-related
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".
* The Magic "Fill" Tool Looks Bad
To change this, you must rebuild Tux Paint from source.
Be sure to remove or comment out any line that says:
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".
#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
------------------------------------
Tux Paint was built with low-quality (but faster) stamp outlines.
* Stamp outlines are always rectangles
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
Tux Paint was built with low-quality (but faster) stamp outlines.
#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!
------------------------------------
This means that Tux Paint either couldn't find any stamp images,
or was asked not to load them.
* The Rubber Stamp tool is greyed out!
If you installed Tux Paint, but did not install the separate,
optional "Stamps" collection, quit Tux Paint and install it now.
It should be available from the same place you got the main
Tux Paint program.
This means that Tux Paint either couldn't find any stamp images, or
was asked not to load them.
If you don't want to install the default collection of stamps,
you can just create your own. See the README documentation for
more on creating PNG image files, TXT text description files,
WAV sound files, and DAT text data files that make up stamps.
If you installed Tux Paint, but did not install the separate, optional
"Stamps" collection, quit Tux Paint and install it now. It should be
available from the same place you got the main Tux Paint program.
(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,
check to see that the "nostamps" option isn't being set.
(Either via a "--nostamps" option to Tux Paint's command line, or
"nostamps=yes" in the configuration file.)
If you don't want to install the default collection of stamps, you can
just create your own. See the README documentation for more on
creating PNG image files, TXT text description files, WAV sound files,
and DAT text data files that make up stamps.
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.
Finally, if you install the stamps, and think they should be loading,
check to see that the "nostamps" option isn't being set. (Either via a
"--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
------------------
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.
Interface Problems
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
* Stamp thumbnails in the Stamp Selector look bad
#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
--------------------------------------
"Low Quality Thumbnails" is probably enabled.
See: "Stamp thumbnails in the Stamp Selector look bad", above.
in the "tuxpaint.c" file in the "src" directory.
* Pictures in the 'Open' dialog look bad
The color picker buttons are ugly squares, not pretty buttons!
--------------------------------------------------------------
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.
"Low Quality Thumbnails" is probably enabled. See: "Stamp thumbnails
in the Stamp Selector look bad", above.
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
* The color picker buttons are ugly squares, not pretty buttons!
#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 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.
in the "tuxpaint.c" file in the "src" directory.
Until there's a fix, either don't use fullscreen, or disable the
fancy mouse pointer shapes using the configuration option:
* All of the text is in uppercase!
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!
--------------------------------
The "uppercase" option is on.
Either remove that line, or simply run Tux Paint with the command-line
argument: "--mixedcase", which will override the uppercase setting.
If you're running Tux Paint from a command-line, make sure you're
not giving it an "--uppercase" option.
Or use Tux Paint Config. and make sure "Show Uppercase Text Only"
(under "Languages") is not checked.
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.
* Tux Paint is in a different language!
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".
Make sure your locale setting is correct. See "Tux Paint won't switch
to my language", below.
Either remove that line, or simply run Tux Paint with the command-line
argument: "--mixedcase", which will override the uppercase setting.
* Tux Paint won't switch to my language
* Linux and Unix users: Make sure the locale is available
Tux Paint is in a weird language!
---------------------------------
Make sure your locale setting is correct.
See "Tux Paint won't switch to my language", below.
Make sure the locale you want is available. Check your
"/etc/locale.gen" file. See the README documentation for the
locales Tux Paint uses (especially when using the "--lang"
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
-------------------------------------
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).
* If you're using the "--lang" command-line option
Note: Debian users can simply run "dpkg-reconfigure locales"
if the locales are managed by dpkg.
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 "--lang" 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 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 this doesn't work, please e-mail us regarding your trouble.
* If you're trying to use your Operating System's locale
Make sure you have the necessary font
-------------------------------------
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.
If this doesn't work, please e-mail us regarding your
trouble.
The appropriate fonts for such locales can be downloaded from the
Tux Paint website:
* Make sure you have the necessary font
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
--------
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.
http://www.newbreedsoftware.com/tuxpaint/download/fonts/
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.)
Printing
Note: Versions of Tux Paint prior to 0.9.15 used a different default
command for printing, "pngtopnm | pnmtops | lpr", as Tux Paint output
PNG format, rather than PostScript.
* Tux Paint won't print, gives an error, or prints garbage (Unix/Linux)
If you had changed your "printcommand" option prior to Tux Paint 0.9.15,
you will need to go back and alter it to accept PostScript.
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, 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!
------------------------------------------------------------
The "print delay" option is on. You can only print once every X seconds.
Note: Versions of Tux Paint prior to 0.9.15 used a different default
command for printing, "pngtopnm | pnmtops | lpr", as Tux Paint output
PNG format, rather than PostScript.
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--printdelay=..." option.
If you had changed your "printcommand" option prior to Tux Paint
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
properties of the icon to see if "--printdelay=..." is listed as
a command-line argument.
* I get the message "You can't print yet!" when I go to print!
If a "--printdelay=..." option 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:
"printdelay=...".
The "print delay" option is on. You can only print once every
X seconds.
Either remove that line, set the delay value to 0 (no delay), or
decrease the delay to a value you prefer. (See README.txt).
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 from a command-line, make sure you're not
giving it a "--printdelay=..." option.
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!
------------------------------------------------
The "no print" option is on.
If a "--printdelay=..." option 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:
"printdelay=...".
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--noprint" option.
Either remove that line, set the delay value to 0 (no delay), or
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
properties of the icon to see if "--noprint" is listed as an argument.
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 "--noprint" 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: "noprint=yes".
Or use Tux Paint Config. and make sure "Print Delay" (under
"Printing") is set to "0 seconds."
Either remove that line, or simply run Tux Paint with the command-line
argument: "--print", which will override the configuration file's setting.
* I simply can't print! The button is greyed out!
The "no print" option is on.
Saving
------
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 not
giving it a "--noprint" option.
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--saveover" option.
If you're running Tux Paint by double-clicking an icon, check the
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
properties of the icon to see if "--saveover" is listed as an argument.
If "--noprint" 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: "noprint=yes".
If "--saveover" 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=yes".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--print", which will override the configuration file's
setting.
Either remove that line, or simply run Tux Paint with the command-line
argument: "--saveoverask", which will override the configuration file's
setting.
Or use Tux Paint Config. and make sure "Allow Printing" (under
"Printing") is checked.
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 "never save over" option is enabled. (This disables the prompt
that would appear when you click 'Save.')
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
not giving it a "--saveovernew" option.
If you're running Tux Paint from a command-line, make sure you're not
giving it a "--saveover" option.
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 you're running Tux Paint by double-clicking an icon, check the
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
configuration file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg"
under Windows) for a line reading: "saveover=new".
If "--saveover" 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=yes".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--saveoverask", which will override the configuration file's
setting.
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.
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
--------------
There's no sound!
-----------------
First, check the obvious:
* Tux Paint always saves a new picture!
* 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)
The "never save over" option is enabled. (This disables the prompt
that would appear when you click 'Save.')
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.
If you're running Tux Paint from a command-line, make sure you're not
giving it a "--saveovernew" option.
To test whether sound support was enabled when Tux Paint was compiled,
run Tux Paint from a command line, like so:
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.
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
version of Tux Paint you're running has sound disabled. Recompiled
Tux Paint, and be sure NOT to build the "nosound" target.
(i.e., don't run "make nosound") Be sure SDL_mixer library is available!
Either remove that line, or simply run Tux Paint with the command-line
argument: "--saveoverask", which will override the configuration
file's setting.
If Tux Paint wasn't build without sound support, make sure you're
not running Tux Paint with the "--nosound" option as a command-line
argument.
Or use Tux Paint Config. and make sure "Ask Before Overwriting" (under
"Saving") is checked.
If it's not, then check the configuration file ("~/.tuxpaintrc" under
Linux and Unix, and "tuxpaint.cfg" under Windows) for a line reading:
"nosound=yes".
Also, see "Tux Paint always saves over my old picture!", above.
Either remove that line, or simply run Tux Paint with the command-line
argument: "--sound", which will override the configuration file's setting.
Audio Problems
* There's no sound!
The sound effects sound strange
-------------------------------
This could have to do with how SDL and SDL_mixer were initialized.
(The buffer size chosen.)
First, check the obvious:
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.)
* 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)
* (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
------------------------
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.
To test whether sound support was enabled when Tux Paint was compiled,
run Tux Paint from a command line, like so:
tuxpaint --version
When I run Tux Paint full-screen, it has large borders around it
----------------------------------------------------------------
Linux users - Your X-Window server is probably not set with the
ability to switch to the desired resolution: 640 x 480.
(This is typically done manually under the XFree86 server by
pressing [Ctrl]-[Alt]-[KeyPad Plus] and -[KeyPad Minus].)
If, amongst the other information, you see "Sound disabled", then the
version of Tux Paint you're running has sound disabled. Recompile
Tux Paint, and be sure NOT to build the "nosound" target. (i.e., don't
run "make nosound") Be sure the SDL_mixer library and its development
headers are available!
For this to work, your monitor must support that resolution, and
you need to have it listed in your X server configuration.
If Tux Paint wasn't build without sound support, make sure you're not
running Tux Paint with the "--nosound" option as a command-line
argument.
Check the "Display" subsection of the "Screen" section of your
XFree86 configuration file (typically "/etc/X11/XF86Config-4" or
"/etc/X11/XF86Config", depending on the version of XFree86 you're
using; 3.x or 4.x, respectively).
If it's not, then check the configuration file ("~/.tuxpaintrc" under
Linux and Unix, and "tuxpaint.cfg" under Windows) for a line reading:
"nosound=yes".
Add "640x480" to the appropriate "Modes" line. (e.g., in
the "Display" subsection that contains 16-bit color depth ("Depth 16"),
which is what Tux Paint tries to use.)
Either remove that line, or simply run Tux Paint with the command-line
argument: "--sound", which will override the configuration file's
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
changes for you. Debian users can run the command
"dpkg-reconfigure xserver-xfree86" as root, for example.
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. (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!
-----------------------------------------------------------------
The "fullscreen" option is set.
Fullscreen Mode Problems
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--fullscreen" option.
* When I run Tux Paint full-screen and ALT-TAB out, the window turns
black!
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--fullscreen" is listed as an argument.
This is apparently a bug in the SDL library. Sorry.
If "--fullscreen" 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: "fullscreen=yes".
* When I run Tux Paint full-screen, it has large borders around it
Either remove that line, or simply run Tux Paint with the command-line
argument: "--windowed", which will override the configuration file's
setting.
Linux users - Your X-Window server is probably not set with the
ability to switch to the desired resolution: 800×600. (or whatever
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
--------------
Tux Paint won't run
-------------------
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.
Check the "Display" subsection of the "Screen" section of your XFree86
or X.org configuration file (typically "/etc/X11/XF86Config-4" or
"/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).
A lockfile ("~/.tuxpaint/lockfile.dat" on Linux and Unix,
"userdata\lockfile.dat" on Windows) is used to make sure Tux Paint
isn't run too many times at once (e.g., due to a child impatiently
clicking its icon more than once).
Add "800x600" (or whatever resolution(s) you want) to the appropriate
"Modes" line. (e.g., in the "Display" subsection that contains 24-bit
color depth ("Depth 24"), which is what Tux Paint tries to use.) e.g.:
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.
Modes "1280x1024" "1024x768" "800x600" "640x480"
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
feature.
Note that some Linux distributions have tools that can make these
changes for you. Debian users can run the command "dpkg-reconfigure
xserver-xfree86" as root, for example.
To disable the lockfile, add the "--nolockfile" argument to Tux Paint's
command-line.
* Tux Paint keeps running in Full Screen mode - I want it windowed!
The "fullscreen" option is set.
I can't quit Tux Paint
----------------------
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 you're running Tux Paint from a command-line, make sure you're not
giving it a "--fullscreen" option.
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.)
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--fullscreen" is listed as an
argument.
If Tux Paint is in fullscreen mode, you will need to use the
[Shift] + [Control] + [Escape] sequence on the keyboard to
quit Tux Paint.
If "--fullscreen" 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: "fullscreen=yes".
(Note: with or without "noquit" set, you can always use the
[Alt] + [F4] combination on your keyboard to quit Tux Paint.)
Either remove that line, or simply run Tux Paint with the command-line
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!
-----------------------------------
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--noquit" option.
Other Probelms
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.
* Tux Paint won't run
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".
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. (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
argument: "--quit", which will override the configuration file's
setting.
A lockfile ("~/.tuxpaint/lockfile.dat" on Linux and Unix,
"userdata\lockfile.dat" on Windows) is used to make sure Tux Paint
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
---------------------------------------------------------------------
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.
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
feature.
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
To disable the lockfile, add the "--nolockfile" argument to
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!
--------------------------------------------
By default, Tux Paint first looks at configuration files for
options.
If Tux Paint is in fullscreen mode, you will need to use the [Shift] +
[Control] + [Escape] sequence on the keyboard to quit Tux Paint.
Unix and Linux
--------------
Under Unix and Linux, it first examines the system-wide
configuration file, located here:
(Note: with or without "noquit" set, you can always use the [Alt] +
[F4] combination on your keyboard to quit Tux Paint.)
/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
-------
Under Windows, Tux Paint first examines the configuration file:
Either remove that line, or simply run Tux Paint with the command-line
argument: "--quit", which will override the configuration file's
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
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.
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
For example, if "/etc/tuxpaint/tuxpaint.conf" includes an option
to disable sound:
#define DEBUG
nosound=yes
in the "tuxpaint.c" file in the "src" directory.
You can reenable sound by either adding this option to your own
".tuxpainrc" file:
* Tux Paint is using options I didn't specify!
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
file by including the following command-line argument:
It then examines the user's personal configuration file:
--nosysconfig
~/.tuxpaintrc
Tux Paint will then only look at "~/.tuxpaintrc" and command-line
arguments to determine what options should be set.
Finally, any options sent as command-line arguments are used.
* 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
--------------
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>
</center>
<pre>
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".
<h2>Drawing-related</h2>
To change this, you must rebuild Tux Paint from source.
Be sure to remove or comment out any line that says:
<ul>
<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
</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
------------------------------------
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:
<p>Rebuild Tux&nbsp;Paint from source. Be sure to remove or comment out any
line that says:</p>
<blockquote><p><code>
#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!
------------------------------------
This means that Tux Paint either couldn't find any stamp images,
or was asked not to load them.
<p>If you installed Tux&nbsp;Paint, but did not install the separate,
optional "Stamps" collection, quit Tux&nbsp;Paint and install it now.
It should be available from the same place you got the main
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,
optional "Stamps" collection, quit Tux Paint and install it now.
It should be available from the same place you got the main
Tux Paint program.
<p>If you don't want to install the default collection of stamps,
you can just create your own. See the <a href="README.html">README
documentation</a> for more on creating PNG image files, TXT text
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,
you can just create your own. See the README documentation for
more on creating PNG image files, TXT text description files,
WAV sound files, and DAT text data files that make up stamps.
<p>Finally, if you install the stamps, and think they should be loading,
check to see that the "nostamps" option isn't being set.
(Either via a "--nostamps" option to Tux&nbsp;Paint's command line, or
"nostamps=yes" in the configuration file.)</p>
Finally, if you install the stamps, and think they should be loading,
check to see that the "nostamps" option isn't being set.
(Either via a "--nostamps" option to Tux Paint's command line, or
"nostamps=yes" in the configuration file.)
<p>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.</p>
</li>
</ul>
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.
<h2>Interface Problems</h2>
<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
------------------
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:
<p>Rebuild Tux&nbsp;Paint from source. Be sure to remove or comment out any
line that says:</p>
<blockquote><p><code>
#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
--------------------------------------
"Low Quality Thumbnails" is probably enabled.
See: "Stamp thumbnails in the Stamp Selector look bad", above.
<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
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.</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!
--------------------------------------------------------------
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:
<blockquote><p><code>
#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!
--------------------------------
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.
<p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
not giving it an "--uppercase" option.</p>
Until there's a fix, either don't use fullscreen, or disable the
fancy mouse pointer shapes using the configuration option:
<p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
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!
--------------------------------
The "uppercase" option is on.
<li><em>Tux&nbsp;Paint won't switch to my language</em>
<ul>
<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
not giving it an "--uppercase" option.
<p>Note: Debian users can simply run "dpkg-reconfigure locales"
if the locales are managed by "dpkg."</p>
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.
<ul>
<li>If you're using the "--lang" command-line option
<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
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "uppercase=yes".
<li>If you're using the "--locale" command-line option
<p>If this doesn't work, please e-mail us regarding your trouble.</p>
</li>
Either remove that line, or simply run Tux Paint with the command-line
argument: "--mixedcase", which will override the uppercase setting.
<li>If you're trying to use your Operating System's locale
<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!
---------------------------------
Make sure your locale setting is correct.
See "Tux Paint won't switch to my language", below.
<p>The appropriate fonts for such locales can be downloaded from the
Tux&nbsp;Paint website:</p>
<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
-------------------------------------
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).
<h2>Printing</h2>
<ul>
<li><em>Tux&nbsp;Paint won't print, gives an error, or prints garbage
(Unix/Linux)</em>
<p>Tux&nbsp;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.</p>
Note: Debian users can simply run "dpkg-reconfigure locales"
if the locales are managed by dpkg.
<p>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&nbsp;Paint's configuration file.
(See the <a href="OPTIONS.html">OPTIONS documentation</a>.)</p>
If you're using the "--lang" 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.
<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",
as Tux&nbsp;Paint output PNG format, rather than PostScript.</p>
If you're using the "--locale" command-line option
--------------------------------------------------
If this doesn't work, please e-mail us regarding your trouble.
<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>
</li>
If you're trying to use your Operating System's locale
------------------------------------------------------
If this doesn't work, please e-mail us regarding your trouble.
<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
<i>X</i>&nbsp;seconds.</p>
Make sure you have the necessary font
-------------------------------------
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>If you're running Tux&nbsp;Paint from a command-line, make sure you're
not giving it a "--printdelay=..." option.</p>
The appropriate fonts for such locales can be downloaded from the
Tux Paint website:
<p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
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
--------
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.
<p>Or, you can simply run Tux&nbsp;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 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.)
<p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
"Print Delay" (under "Printing") is set to "0&nbsp;seconds."</p>
</li>
Note: Versions of Tux Paint prior to 0.9.15 used a different default
command for printing, "pngtopnm | pnmtops | lpr", as Tux Paint output
PNG format, rather than PostScript.
<li><em>I simply can't print! The button is greyed out!</em>
<p>The "no print" option is on.</p>
If you had changed your "printcommand" option prior to Tux Paint 0.9.15,
you will need to go back and alter it to accept PostScript.
<p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
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!
------------------------------------------------------------
The "print delay" option is on. You can only print once every X seconds.
<p>If "--noprint" 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: "noprint=yes".</p>
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--printdelay=..." option.
<p>Either remove that line, or simply run Tux&nbsp;Paint with the
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
properties of the icon to see if "--printdelay=..." is listed as
a command-line argument.
<p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
"Allow Printing" (under "Printing") is checked.</p>
</li>
</ul>
If a "--printdelay=..." option 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:
"printdelay=...".
<h2>Saving</h2>
<ul>
<li><em>Tux&nbsp;Paint always saves over my old picture!</em>
<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
decrease the delay to a value you prefer. (See README.txt).
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 from a command-line, make sure you're
not giving it a "--saveover" option.</p>
<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!
------------------------------------------------
The "no print" option is on.
<p>If "--saveover" 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: "saveover=yes".</p>
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--noprint" option.
<p>Either remove that line, or simply run Tux&nbsp;Paint with the
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
properties of the icon to see if "--noprint" is listed as an argument.
<p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
"Ask Before Overwriting" (under "Saving") is checked.</p>
If "--noprint" 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: "noprint=yes".
<p>Also, see "Tux&nbsp;Paint always saves a new picture!", below.</p>
</li>
Either remove that line, or simply run Tux Paint with the command-line
argument: "--print", which will override the configuration file's setting.
<li><em>Tux&nbsp;Paint always saves a new picture!</em>
<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
------
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.')
<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
argument.</p>
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--saveover" option.
<p>If "--saveovernew" 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: "saveover=new".</p>
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--saveover" is listed as an argument.
<p>Either remove that line, or simply run Tux&nbsp;Paint with the
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
file ("~/.tuxpaintrc" under Linux and Unix, "tuxpaint.cfg" under Windows)
for a line reading: "saveover=yes".
<p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
"Ask Before Overwriting" (under "Saving") is checked.</p>
Either remove that line, or simply run Tux Paint with the command-line
argument: "--saveoverask", which will override the configuration file's
setting.
<p>Also, see "Tux&nbsp;Paint always saves over my old picture!", above.</p>
</li>
</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!
-------------------------------------
The "never save over" option is enabled. (This disables the prompt
that would appear when you click 'Save.')
<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
a "no sound" option or was compiled with sound support disabled entirely.</p>
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--saveovernew" option.
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:
<p>To test whether sound support was enabled when Tux&nbsp;Paint was
compiled, run Tux&nbsp;Paint from a command line, like so:</p>
<blockquote><p><code>
tuxpaint --version
</code></p></blockquote>
If, amongst the other information, you see "Sound disabled", then the
version of Tux Paint you're running has sound disabled. Recompiled
Tux Paint, and be sure NOT to build the "nosound" target.
(i.e., don't run "make nosound") Be sure SDL_mixer library is available!
<p>If, amongst the other information, you see "Sound disabled", then the
version of Tux&nbsp;Paint you're running has sound disabled. Recompile
Tux&nbsp;Paint, and be sure NOT to build the "nosound" target.
(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
not running Tux Paint with the "--nosound" option as a command-line
argument.
<p>If Tux&nbsp;Paint wasn't build without sound support, make sure you're
not running Tux&nbsp;Paint with the "--nosound" option as a command-line
argument.</p>
If it's not, then check the configuration file ("~/.tuxpaintrc" under
Linux and Unix, and "tuxpaint.cfg" under Windows) for a line reading:
"nosound=yes".
<p>If it's not, then check the configuration file ("~/.tuxpaintrc" under
Linux and Unix, and "tuxpaint.cfg" under Windows) for a line reading:
"nosound=yes".</p>
Either remove that line, or simply run Tux Paint with the command-line
argument: "--sound", which will override the configuration file's setting.
<p>Either remove that line, or simply run Tux&nbsp;Paint with the
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
-------------------------------
This could have to do with how SDL and SDL_mixer were initialized.
(The buffer size chosen.)
<li><em>The sound effects sound strange</em>
<p>This could have to do with how SDL and SDL_mixer were initialized.
(The buffer size chosen.)</p>
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.)
<p>Please e-mail us with details about your computer system.
(Operating system and version, sound card, which version of Tux&nbsp;Paint
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
------------------------
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.
<p>This is apparently a bug in the SDL library. Sorry.</p>
<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
----------------------------------------------------------------
Linux users - Your X-Window server is probably not set with the
ability to switch to the desired resolution: 640 x 480.
(This is typically done manually under the XFree86 server by
pressing [Ctrl]-[Alt]-[KeyPad Plus] and -[KeyPad Minus].)
<p>Linux users - Your X-Window server is probably not set with the
ability to switch to the desired resolution: 800&times;600.
(or whatever resolution you have Tux&nbsp;Paint set to run at.)
(This is typically done manually under the X-Window server by
pressing [Ctrl]-[Alt]-[KeyPad Plus] and -[KeyPad Minus].)</p>
For this to work, your monitor must support that resolution, and
you need to have it listed in your X server configuration.
<p>For this to work, your monitor must support that resolution, and
you need to have it listed in your X server configuration.</p>
Check the "Display" subsection of the "Screen" section of your
XFree86 configuration file (typically "/etc/X11/XF86Config-4" or
"/etc/X11/XF86Config", depending on the version of XFree86 you're
using; 3.x or 4.x, respectively).
<p>Check the "Display" subsection of the "Screen" section of your
XFree86 or X.org configuration file (typically "/etc/X11/XF86Config-4" or
"/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).</p>
Add "640x480" to the appropriate "Modes" line. (e.g., in
the "Display" subsection that contains 16-bit color depth ("Depth 16"),
which is what Tux Paint tries to use.)
e.g.:
<p>Add "800x600" (or whatever resolution(s) you want) to the appropriate
"Modes" line. (e.g., in the "Display" subsection that contains 24-bit color
depth ("Depth&nbsp;24"), which is what Tux&nbsp;Paint tries to use.)
e.g.:<p>
<blockquote><p><code>
Modes "1280x1024" "1024x768" "800x600" "640x480"
</code></p></blockquote>
Note that some Linux distributions have tools that can make these
changes for you. Debian users can run the command
"dpkg-reconfigure xserver-xfree86" as root, for example.
<p>Note that some Linux distributions have tools that can make these
changes for you. Debian users can run the command
"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!
-----------------------------------------------------------------
The "fullscreen" option is set.
<p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
not giving it a "--fullscreen" option.</p>
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--fullscreen" option.
<p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
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
properties of the icon to see if "--fullscreen" is listed as an argument.
<p>If "--fullscreen" 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: "fullscreen=yes".</p>
If "--fullscreen" 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: "fullscreen=yes".
<p>Either remove that line, or simply run Tux&nbsp;Paint with the
command-line argument: "--windowed", which will override the configuration
file's setting.</p>
Either remove that line, or simply run Tux Paint with the command-line
argument: "--windowed", which will override the configuration file's
setting.
<p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
"Fullscreen" (under "Video &amp; Sound") is not checked.</p>
</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
--------------
Tux Paint won't run
-------------------
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.
<p>A lockfile ("~/.tuxpaint/lockfile.dat" on Linux and Unix,
"userdata\lockfile.dat" on Windows) is used to make sure Tux&nbsp;Paint
isn't run too many times at once (e.g., due to a child impatiently
clicking its icon more than once).</p>
A lockfile ("~/.tuxpaint/lockfile.dat" on Linux and Unix,
"userdata\lockfile.dat" on Windows) is used to make sure Tux Paint
isn't run too many times at once (e.g., due to a child impatiently
clicking its icon more than once).
<p>Even if the lockfile exists, it contains the 'time' Tux&nbsp;Paint was
last run. If it's been more than 30 seconds, Tux&nbsp;Paint should run fine,
and simply update the lockfile with the current time.</p>
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.
<p>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
feature.</p>
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
feature.
<p>To disable the lockfile, add the "--nolockfile" argument to
Tux&nbsp;Paint's command-line.</p>
</li>
To disable the lockfile, add the "--nolockfile" argument to Tux Paint's
command-line.
<li><em>I can't quit Tux&nbsp;Paint</em>
<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
----------------------
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.
<p>If Tux&nbsp;Paint is in fullscreen mode, you will need to use the
[Shift] + [Control] + [Escape] sequence on the keyboard to
quit Tux&nbsp;Paint.</p>
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.)
<p>(Note: with or without "noquit" set, you can always use the
[Alt] + [F4] combination on your keyboard to quit Tux&nbsp;Paint.)</p>
</li>
If Tux Paint is in fullscreen mode, you will need to use the
[Shift] + [Control] + [Escape] sequence on the keyboard to
quit Tux Paint.
<li><em>I don't want "noquit" mode enabled!</em>
<p>If you're running Tux&nbsp;Paint from a command-line, make sure you're
not giving it a "--noquit" option.</p>
(Note: with or without "noquit" set, you can always use the
[Alt] + [F4] combination on your keyboard to quit Tux Paint.)
<p>If you're running Tux&nbsp;Paint by double-clicking an icon, check the
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!
-----------------------------------
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--noquit" option.
<p>Either remove that line, or simply run Tux&nbsp;Paint with the
command-line argument: "--quit", which will override the configuration file's
setting.</p>
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.
<p>Or use Tux&nbsp;Paint&nbsp;Config. and make sure
"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
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "noquit=yes".
<li><em>Tux&nbsp;Paint keeps writing weird messages to the screen / to a text
file</em>
<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
argument: "--quit", which will override the configuration file's
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:
<p>Rebuild Tux&nbsp;Paint from source. Be sure to remove or comment out any
line that says:</p>
<blockquote><p><code>
#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!
--------------------------------------------
By default, Tux Paint first looks at configuration files for
options.
Unix and Linux
--------------
Under Unix and Linux, it first examines the system-wide
configuration file, located here:
<ul>
<li><i>Unix and Linux</i>
<p>Under Unix and Linux, it first examines the system-wide
configuration file, located here:</p>
<blockquote><p><code>
/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
</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
-------
Under Windows, Tux Paint first examines the configuration file:
<li><i>Windows</i>
<p>Under Windows, Tux&nbsp;Paint first examines the configuration file:</p>
<blockquote><p><code>
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
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:
<p>For example, if "/etc/tuxpaint/tuxpaint.conf" includes an option
to disable sound:</p>
<blockquote><p><code>
nosound=yes
</blockquote></p></code>
You can reenable sound by either adding this option to your own
".tuxpainrc" file:
<p>You can reenable sound by either adding this option to your own
".tuxpainrc" file:</p>
<blockquote><p><code>
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
</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
file by including the following command-line argument:
<blockquote><p><code>
--nosysconfig
</blockquote></p></code>
Tux Paint will then only look at "~/.tuxpaintrc" and command-line
arguments to determine what options should be set.
<p>Tux&nbsp;Paint will then only look at "~/.tuxpaintrc" and command-line
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
--------------
Any questions you don't see answered? Let me know!
<blockquote><p><a href="mailto:bill@newbreedsoftware.com"
>bill@newbreedsoftware.com</a></p></blockquote>
bill@newbreedsoftware.com
<p>Or post to our 'tuxpaint-users' mailing list:</p>
Or post to our 'tuxpaint-dev' mailing list:
http://www.newbreedsoftware.com/tuxpaint/lists/
</pre>
<blockquote><p><a href="http://www.newbreedsoftware.com/tuxpaint/lists/"
>http://www.newbreedsoftware.com/tuxpaint/lists/</a></p></blockquote>
</body></html>