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 749488 - Save vs. Export
Save vs. Export
Status: RESOLVED DUPLICATE of bug 581655
Product: GIMP
Classification: Other
Component: User Interface
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-05-17 06:00 UTC by Burkhard Arenfeld
Modified: 2015-05-18 07:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Burkhard Arenfeld 2015-05-17 06:00:48 UTC
Dear Gimp Team.

This is not a real bug but a petition to think again if this change was real a
good thing. As a long-time-user of Gimp I'm angry about the split of the save and export menu into different entries.
The XCF format is a great thing to save the work if I want to edit the image again later. But if I'm opening a jpeg image I normally do some work on it and - of course - I want to save it back in the jpeg format.
In the last version I only need to use the save menu, got a warning if some informations was lost because jpeg format doesn't support it and everything was OK.
Now I need to use the export dialog (and need to remember another shortcut instead the one I used for nearly 17 years ...) and after that the image is still not marked as saved and I got a warning every time I want to close it.
This is very annoying and confusing especially if I'm working on more than one image at the same time.

PLEASE if you don't are willing to merge the menus back into one,
at least make an option switch that "Exported images" are marked as clean 
and the "Not saved" warning is not popping up.

Greetings

B.A.
Comment 1 Michael Schumacher 2015-05-18 07:50:50 UTC
Yes, we think this is a good thing: http://gui.gimp.org/index.php/Save_%2B_export_specification

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