After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 134990 - TGA save settings not remembered
TGA save settings not remembered
Status: RESOLVED DUPLICATE of bug 63610
Product: GIMP
Classification: Other
Component: Plugins
1.x
Other Windows
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-02-20 20:29 UTC by ju92kqj02
Modified: 2005-04-29 16:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description ju92kqj02 2004-02-20 20:29:21 UTC
Hello,

I have found the tga save settings to be rather limited. I would like to
suggest some revisions to make it more usable.

Some things I think should be improved:
1. If a tga is loaded as an "uncompressed tga" with "origin bottom left",
when I click "save" the output file should also be an "uncompressed tga". 
Not "RLE" and not "origin top left"...

2. If a user "save as" for a tga file,  and the input image was
"uncompressed tga" with "origin bottom left" the tga save options should
default to the same "uncompressed tga" with "origin bottom left"  format..

3.  If a user "save as" for a tga file, and turns off the default "RLE tga"
with "origin top left" then this should be saved in a gimp settings file so
that the next time a user does this it defaults to their preferred tga format.


Kind regards



I replicated this bug with:
gimp-2.0-pre2-i686-setup.zip
gtk+-2.2.4-setup-2.zip
Comment 1 Raphaël Quinet 2004-02-20 21:07:50 UTC
Your examples 1 and 2 are basically the same and could be an interesting
addition to the TGA plug-in.

The example 3 is different and is wrong from my point of view: what you
do when saving an image should not alter the defaults that are used for
saving other images.  But this can be solved by allowing some settings
(presets) to be saved (by an explicit action of the user) and re-used
for other images.  This is already covered by bug #63610 and bug #120829
so let's keep this out of this bug report and focus on your first two
examples.
Comment 2 ju92kqj02 2004-02-24 20:14:56 UTC
Hello Raphaël Quinet

Thanks for your feedback to my suggestions.  Sounds like (3) is
covered then.  Something like a tick box "[x] Save as default
settings" would be great :)

For my (1) and (2) suggestions, do you think this could be workable?
to store the settings when a file is loaded, (the tga plug-in settings
are presently stored while gimp is in memory only from what I can
tell, as my settings are remembered between multiple "save as", but
not "save")

Thanks for confirming as NEW.

Kind regards
Comment 3 Daniel Lublin 2004-05-25 10:50:15 UTC
Somewhat related:

I open a TIFF image, I'm not sure what the compression
type is.

Then I edit the image.

Then "Save as" anewname.tiff; in the TIFF options box,
LZW is the default (because the original was LZW?).
Anyway, because of the patent and GIMP not being able
to do LZW compression, I choose deflate.

I do some more editing.

Then I do "Save", GIMP tries to do LZW compression,
reports the failure, but it does write to the disk;
the resulting anewname.tiff is 8 (or so) bytes big.

1. I don't think it should do LZW here, I did a Save-as
with deflate, and I would assume that Save would try
the same options.

2. If it fails, why does it write to the disk,
destroying my image? A couple of times I did not care
about my second edits, when the second save failed,
so I quit gimp. Just to find that my image was gone.
Now I have learned...

Perhaps this is really bug #63610. But it seems that
the settings are not kept even during the same session...
Comment 4 Sven Neumann 2004-05-25 12:33:34 UTC
Sorry but why can't your TIFF plug-in do LZW compression? The only reason I can
think of is that your distributor patched the plug-in. In that case he's done a
very bad job at this and should be blamed for it.
Comment 5 Sven Neumann 2004-12-06 12:11:52 UTC
The summary of this report should be changed. As it stands it looks like a
duplicate of bug #63610.
Comment 6 Sven Neumann 2005-04-29 16:50:14 UTC
Closing this report since obviously part of the problem was caused by a patched
TIFF plug-in and the other part is handled in bug #63610.

*** This bug has been marked as a duplicate of 63610 ***