RSS/Atom feed Twitter
Site is read-only, email is disabled

Save vs export separate discussion forum needed

This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 4 messages available
Toggle history

Please log in to manage your subscriptions.

98B5369C-F6F8-4E08-9968-C68... 20 Jul 16:20
  Save vs export separate discussion forum needed Richard Gitschlag 20 Jul 16:19
   Save vs export separate discussion forum needed Sam Gleske 22 Jul 22:02
51E9D712.7040902@JaySmith.com 22 Jul 22:03
Richard Gitschlag
2013-07-20 16:19:12 UTC (over 11 years ago)

Save vs export separate discussion forum needed

From: kasim.ahmic@gmail.com
Date: Fri, 19 Jul 2013 20:28:08 -0400 To: jay@JaySmith.com
CC: gimp-user-list@gnome.org
Subject: Re: [Gimp-user] Save vs export separate discussion forum needed

What you're saying does make sense but is it really necessary? I mean is it really THAT difficult to get accustomed to the new way of working? It's not even that big of a change, IMO. Just a different option to click really.

Sent from my iPod

Part of the annoyance was recently stated by another user: If your particular GIMP workflow (for whatever reason) has little to no need of XCF file storage, GIMP still bombards you with "Save changes?" dialogs every time you close an image after doing your work on it. Even months or years after mentally adjusting to the Export command, this dialog persists and you learn to ignore it out of simple habit -- GIMP is crying wolf. That is bad.

IMHO GIMP could benefit from re-instating the user preference that was "confirm closing of unsaved images", but not as it previously was. The preference would still be enabled by default, but if it's disabled, then for a given image: - If the image belongs to an XCF file, GIMP ignores the preference and always prompts for unsaved changes (saving them to the XCF file, of course). - If there is no XCF file associated with the image (typical of import/export/overwrite type workflow), GIMP will only prompt to save changes if there are changes since the last export. If there are none, GIMP will not prompt the user (crying wolf scenario).

I know I haven't thought out this one completely, but it would help eliminate a problem with how GIMP treats the non-XCF workflow, it would not affect XCF-based workflows, and would not affect the distinction between Save and Export.

-- Stratadrake strata_ranger@hotmail.com
--------------------
Numbers may not lie, but neither do they tell the whole truth.

Sam Gleske
2013-07-22 22:02:14 UTC (over 11 years ago)

Save vs export separate discussion forum needed

On Sat, Jul 20, 2013 at 12:19 PM, Richard Gitschlag < strata_ranger@hotmail.com> wrote:\

Part of the annoyance was recently stated by another user: If your particular GIMP workflow (for whatever reason) has little to no need of XCF file storage, GIMP still bombards you with "Save changes?" dialogs every time you close an image after doing your work on it. Even months or years after mentally adjusting to the Export command, this dialog persists and you learn to ignore it out of simple habit -- GIMP is crying wolf. That is bad.

I agree with this sentiment about asking to save too often. Though I do like the new export feature when I'm not working with XCF it is a bit of an annoyance.

IMHO GIMP could benefit from re-instating the user preference that was "confirm closing of unsaved images", but not as it previously was. The preference would still be enabled by default, but if it's disabled, then for a given image:
- If the image belongs to an XCF file, GIMP ignores the preference and always prompts for unsaved changes (saving them to the XCF file, of course). - If there is no XCF file associated with the image (typical of import/export/overwrite type workflow), GIMP will only prompt to save changes if there are changes since the last export. If there are none, GIMP will not prompt the user (crying wolf scenario).

I was thinking about this as well. I think it would be a nice preference to have. It wouldn't change the UI but would modify the repetitive "save your work" routine. I've actually accidentally closed unsaved changes on that for minor tweaks. While it's no big deal because it was an easily repeatable action it's still something I had to take the time to do over again and disrupts my workflow in that specific scenario.

SAM