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 331263 - Choice to always create a new version
Choice to always create a new version
Status: RESOLVED WONTFIX
Product: f-spot
Classification: Other
Component: Editing
CVS
Other All
: Normal enhancement
: ---
Assigned To: F-spot maintainers
F-spot maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-02-15 11:17 UTC by Bengt Thuree
Modified: 2018-07-12 00:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bengt Thuree 2006-02-15 11:17:26 UTC
Please describe the problem:
If you are working on a version of the photo (not the original), and choose to
crop it, or change the color or something, a new version is not created. F-Spot
is re-using the current version.

Steps to reproduce:
1. Double click a photo to get into edit mode.
2. Crop the photo --> a new version is created, and beeing used.
3. Change to B/W, Sepia or crop photo. A new version is not created.


Actual results:
A new photo version is not created.

Expected results:
A new version of the photo.

Does this happen every time?
Yes

Other information:
Comment 1 Gabriel Burt 2006-02-20 05:58:15 UTC
F-Spot does this for almost every type of edit, I believe.  I can see that you may want it to create a new version every time, but a lot of people wouldn't.  Perhaps there could be a "Lock version" option that would make it so any edits would first create another version?  Besides that possible feature request, I don't really think this is a bug.
Comment 2 Bengt Thuree 2006-02-20 06:17:56 UTC
Ok, I can buy this reasoning :)

Something for preference perhaps? Something like this?

* Always create a new version when editing. Yes/No (where No gives Only create a new version if based upon Original)


Changing to Enhancement request and modifying title to reflect this.
(Trying to anyway :) )
Comment 3 Ryan Hayle 2006-03-06 04:16:24 UTC
Perhaps a better approach would be to have a "save version" command that can be optionally used after each edit, so that several operations can be combined into a single version, but that multiple versions will still be created on subsequent edits.
Comment 4 Bengt Thuree 2006-03-06 04:24:26 UTC
Regarding #3 : Difficult to implement as as soon as you hit the crop button the picture is saved with the current name. At least as it is implemented today.

But if it can be implemented in a good way, would solve this problem.
Comment 5 Bengt Thuree 2007-11-26 17:34:19 UTC
I would recommend adding a gconf key, and implementing comment #2
Comment 6 André Klapper 2018-07-12 00:08:09 UTC
F-Spot has moved to https://github.com/f-spot/f-spot/issues

If this Bugzilla ticket is still valid in a recent version of F-Spot, please feel free to post this topic as a ticket in the F-Spot project on GitHub.

Closing this report as WONTFIX as part of Bugzilla Housekeeping as we are planning to shut down GNOME Bugzilla in favor of GNOME Gitlab.