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 795698 - Some way to "fix" original state of image in memory
Some way to "fix" original state of image in memory
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: General
2.10.0
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2018-04-30 14:12 UTC by Alexandre Prokoudine
Modified: 2018-05-24 19:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alexandre Prokoudine 2018-04-30 14:12:40 UTC 
A user reports:

When GIMP goes beyond the undo steps limit, it is impossible to return to the original state, once save/export to the original file has been done (and thus file > revert does not apply either). It would be desirable if the original state would be always in the memory, so that no matter how far you go past the undo steps limit, you would always be able to return to the original by clicking the topmost item in the Undo History docker.
Comment 1 Jehan 2018-05-05 14:33:17 UTC 
I agree this would be useful. Especially since the first item in the Undo history is called "[Base Image]" so it always made sense to me that it should revert to the opening state.
Comment 2 Elle Stone 2018-05-05 15:07:29 UTC 
+1. Many times I've wished to get back to the original image.
Comment 3 GNOME Infrastructure Team 2018-05-24 19:41:07 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/1396.