#GIF Loader problem ?
Something that most people don't understand (so I better start explaining!)
is that TAD may expand a very tiny file into a very large file as part of
its normal operation. Here's how/why:
If TAD notices an image file contains color (non-grays) it will convert the
image into a 24 bit-plane data set. So, let's say you have a huge image
with only 2 colors (say 2K by 2K with only red and black). Because it is
only two colors the image might be only a few kilobytes on disk…but that
will try to load it in 24 bit-planes by 2K by 2K. That's a HUGE file.
The reason we do this is to allow all those nifty processing capabilities
to work.
Perhaps in a future release we'll have to address this situation in a
better way because you're not the first to comment about it.
At one time…you can either reduce or enlarge but not both. This
restriction allowed us to make some optimizations which really speed up the
most common cases at the expense of the less common case (wanting to expand
and reduce at the same time).
Please keep those comments coming…cuz we're hard at work on Release 2 for
a SomeDay release. Your input is very much appreciated.
pk