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 596901 - RFE: add export state to "close image" warning
RFE: add export state to "close image" warning
Status: RESOLVED DUPLICATE of bug 675399
Product: GIMP
Classification: Other
Component: User Interface
git master
Other All
: Normal minor
: 2.8
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2009-09-30 18:10 UTC by liam
Modified: 2012-10-07 16:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description liam 2009-09-30 18:10:35 UTC
If you close an image that's been changed since it was last saved as xcf or xcf.gz, you get a warning box,

    Save the changes to image 'img_7047-bw-columns.xcf' before closing?

    If you don't save the image, changes from the last 9 minutes will be lost

There are the following cases:

(1) File never saved as xcf, but has been exported
    In this case, if the exported file is up to date, jut warn that
    no xcf-format image was saved.
    (for extra points don't do this is the format is lossless and there
    is only one layer)

(2) File has not been saved or exported - warn as now

(3) File has been saved, and exported

3a saved is up to date, exported is not
    warn that the image has been changed since it was last exported,

3b saved is up to date, exported is up to date
   no dialogue in this case :-)

3c saved not up to date, exported is up to date
    warn that the xcf file is not saved, but mention that the
    image has been exported, and give both filenames.

One way for 3 might be a summary:

The image has been changed since it was last saved or exported:
file: foo.jpg
status: changed

file: foo.xcf
status: saved

The goal here is to avoid a dialogue that tells lies - e.g. it says changes will be lost but they are in fact in my final png file - and to avoid data loss - confusion between which of the 2 files is up to date.
Comment 1 Michael Natterer 2012-10-07 16:22:18 UTC
The other bugs should have been dups of this one, but so what.

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