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 119032 - save JPEG quality value in GIMP session
save JPEG quality value in GIMP session
Status: RESOLVED DUPLICATE of bug 63610
Product: GIMP
Classification: Other
Component: Plugins
1.x
Other All
: Normal enhancement
: Future
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2003-08-03 20:29 UTC by ralf hartings
Modified: 2003-11-28 08:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description ralf hartings 2003-08-03 20:29:58 UTC
If you save the same image several times as a jpeg, without closing the
gimp or reverting the image, it keeps the quality value.
However, if you have several pictures in one and the same GIMP session, 
you need to indicate the quality value this for each picture (if you don't
want the std value 0,75). This is what makes working a series of pictures
so tedious and it would be VERY nice if this could be changed.....
Comment 1 Maurits Rijk 2003-08-04 07:14:30 UTC

*** This bug has been marked as a duplicate of 63610 ***
Comment 2 Dave Neary 2003-08-04 12:16:57 UTC
Hi,

This is slightly different to the other bug (the other one refers to
saving settings across sessions, this refers to the easier problem of
saving settings within one session). 

Currently, we have this behaviour:
Open image A
Save as jpeg
Change quality to 90%
Open image B
Save as jpeg
Quality is 75% again

Our choices for keeping this value are fairly straightforward - either
we set up a preference with a default value and no GUI way to change
it (might be an idea), or we create a parasite with global scope to
keep track. 

When we come up with a better idea for making plug-in settings
persistent, then the jpeg settings will fit nicely into that. In the
meantime, the jpeg quality setting should be raised to 85 or 90% by
default, and we should look at keeping the setting within a gimp
session for 2.0.

Cheers,
Dave.
Comment 3 Alan Horkan 2003-08-04 16:01:38 UTC
ideally bug 63610 would fix this but maybe someone will tackle this
lesser task sooner.   
Comment 4 Raphaël Quinet 2003-08-05 08:12:22 UTC
I suggest to close this as WONTFIX or to mark it again as a duplicate
of bug #63610, for the following reasons (which I already hinted at
in bug #61088):

The current model assigns a default setting (which is hardcoded but
should be customizable - see bug #63610) when the image is saved for
the first time.  After this, a parasite is attached to the image so
that it remembers its JPEG settings.  The changes made to other
images will not influence these settings.  The implementation details
(parasites) are not important, but the model is simple to understand:
there is a set of defaults that are used for new images, and the
settings for each image are independent of the other ones.  The
defaults have to be changed by an explicit action of the user (if
bug #63610 is solved) and are not immediately changed when the
settings for one of the current images are changed.

I like the current model because it allows me to work on two images
and save the first one as a progressive JPEG with 90% quality and
the second one as a non-progressive JPEG with 75% quality.  I can
modify each image and save it several times without having to worry
that it would lose its settings after I saved the other one.  I also
know that if I open and save another JPEG image, it will use the
default values that I am familiar with, instead of using some
(possibly unwanted) settings that would depend on whatever I saved
previously.

So from my point of view, the real problem is to allow the user to
customize and save a good set of defaults, as described in bug
#63610.  The interface for doing this still has to be designed: it
could be part of the JPEG plug-in (e.g., "Save default settings") or
part of the Preferences (a tab with some settings for each major file
format) or both.  But in any case, what is done on one image should
not immediately change the settings for the other images.
Comment 5 Raphaël Quinet 2003-11-28 08:28:51 UTC
Since nobody was against the resolution proposed above, I am marking
this again as a duplicate of bug #63610.  Summary of my previous
comment:
- If an image has already been saved at least once in the current
  session, then it should always be saved with its own "save settings",
  regardless of what is changed in the other images.
- When an image has not been saved yet and has no settings (new image
  or image loaded from disk), then it should use the default settings
  for that file format.  It should not be influenced by what is done
  when saving other images.
- There should be a way to change the default settings for each file
  format and to save them accross sessions (bug #63610).

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