On Fri, 04 Feb 2011 16:41:44 +0200, Jeremy Nell wrote:

Is there a way to revert to the original instance?

If you didn't do more edits than the undo system can handle, you can use that, but otherwise no. Revert just means "discard everything since last save".

Jeremy Nell writes:

That's unfortunate.  Sometimes, it is handy to be able to revert to the newly opened file state.

So basically, keep the initially opened file as a "special" persistent undo state, regardless of saves happening in between?

(Emacs does this using backup files... although I guess the user would not want to see lots of HUGEIMAGE.xcf~ files scattered in their directories.)

Hmm, taking that idea further, how about being able to tick off an undo state, and say "don't delete this state no matter how many further actions I do"?

Apropos, http://registry.gimp.net/node/14246 seems like a nice script, although it does not solve this exact problem.

On Fri, 04 Feb 2011 21:00:00 +0530, Jeremy Nell wrote:

How possible is it for someone to create a script / plugin that solves this problem? (Sadly, I know nothing about coding.)

to me the easiest seems to make it a habit to "save as" any image you want to be able to revert to. no scripting required...

"phanisvara das" writes:

On Fri, 04 Feb 2011 21:00:00 +0530, Jeremy Nell wrote:

How possible is it for someone to create a script / plugin that solves this problem? (Sadly, I know nothing about coding.)

to me the easiest seems to make it a habit to "save as" any image you want to be able to revert to. no scripting required...

As a programmer, I find it irking to do the same, repetitive action more than three or four times, when I know that the machine in front of me would uncomplainingly do it a million times if only I gave it the right instructions... but yeah, there is the cost/effect to take into account.

Von: Jeremy Nell

Fair enough, but that's laborious. Why not simply have a history state that, with one click, reverts everything to how it was when you opened it?

See https://bugzilla.gnome.org/show_bug.cgi?id=148930

In general, someone just has to implement something like this (see https://bugzilla.gnome.org/show_bug.cgi?id=51937 for a discussion of macro recording, saving the undo history may be closely related).

Approaches via autosaving should take https://bugzilla.gnome.org/show_bug.cgi?id=138373 into consideration, this report summarizes some of the challenges to be handled.

Regards, Michael

Here's a little script I wrote:
http://registry.gimp.org/node/14246

to do the save-as to a unique file.

I just added a key-binding to call it.

-Rob A>

1. I create an artwork and save it as a Gimp file. 2. I later open it and make changes to it, saving along the way. 3. I then realise that I want to revert to the original state when I opened it.
4. Gimp seems to evert only to the last saved state, rather than the state when I opened it.

Is there a way to revert to the original instance?

There is a gimp plugin 'iterative save' http://registry.gimp.org/node/18873

but you have to invoke the save. still it can be useful.

for once the linux plugin is easy to compile gimptool-2.0 --install .c

1. I create an artwork and save it as a Gimp file. 2. I later open it and make changes to it, saving along the way. 3. I then realise that I want to revert to the original state when I opened it.
4. Gimp seems to evert only to the last saved state, rather than the state when I opened it.

Is there a way to revert to the original instance?

File->Revert