Most file-save plug-ins share a behavior inherited from other plug-ins:they save and retrieve their last values so that invoking them againwill use the same parameters. As discussed previously, this behavioris fine for image filters but leads to annoying consequences for fileplug-ins: if you set some parameters when saving a file, then the sameparameters will be re-used if you save another (unrelated) file withthe same file format during that GIMP session. These settings will beused instead the default values normally set by the plug-in (which maybe user-configurable, as in the PNG and JPEG plug-ins). Today, Jakub Friedl reported in #gimp that this behavior can lead tosurprising results, especially after the changes in the JPEG plug-inthat ensure that the initial quality level for the JPEG save dialog isat least as good as the one from the original image. Because allsettings from the JPEG plug-in (including the quality level) arere-used from one file to the next, the net result is that the qualitylevel always increases if you load and re-save many files that wereoriginally saved with different quality levels. Of course I could just add a quick workaround and change the code thatsets the initial quality level so that it ignores the value coming fromthe "jsvals". But wouldn't it be better to remove the call togimp_get_data (SAVE_PROC, &jsvals) and ignore all these values? Isthere still a reason to keep these shared settings, considering thateach image that has been saved at least once gets its own"jpeg-save-options" parasite, and the user also has the option tochange and save the defaults (which go into a global parasite"jpeg-save-defaults")? -Raphaël_______________________________________________Gimp-developer mailing listGimp-developer@xxxxxxxxxxxxxxxxxxxxxxxxxxx://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
