Bug 291822

Summary:	Saving a versioned image puts it last
Product:	[Applications] digikam	Reporter:	Bruno Randolf <br1>
Component:	ImageEditor-Versioning	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, danni.coy
Priority:	NOR
Version:	2.5.0
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:	4.12.0
Sentry Crash Report:

Description Bruno Randolf 2012-01-18 00:36:43 UTC

Version:           2.5.0 (using KDE 4.6.5) 
OS:                Linux

Saving a new image version in the Image Editor puts it last in the list of images. For example, editing the first image of an album, before saving the status bar of the editor shows NAME.JPG (1 of 10), back and forward keys can be used to jump to the next image. After saving changes to the image, the status bar shows NAME_v1.JPG (10 of 10) and the position is last.

Reproducible: Always

Steps to Reproduce:
* Enable Versioning (Config - Editing Images - Enable non-destructive Editing and Versioning)
* Open image in image editor (Status bar shows something like NAME.JPG (1 of 10))
* Make any change
* Save changes (Status bar shows something like NAME_v1.JPG (10 of 10))


Actual Results:  
We are at the last image, even though it is just a version of the first image.

Expected Results:  
The position should stay on the first image (1 of 10)

Comment 1 Marcel Wiesweg 2012-06-09 13:32:49 UTC

I cannot reproduce this with 2.6, maybe I have worked on this and it is fixed. Can you still reproduce with 2.6?

Comment 2 Danni Coy 2012-06-10 05:55:06 UTC

I can reproduce this is 2.6 - at least the order is getting mixed up and it does seem to be going to the end.

steps to reproduce
1) select an image and press f4 to go into the image editor.
2) use page up and down keys to navigate through the next few images and back.
3) make a change to the image (eg select region and ctrl + x to crop)
4) press save changes 
5) use page up and down keys to try and navigate through the next few images.

Comment 3 Marcel Wiesweg 2012-06-10 16:27:35 UTC

Still cannot reproduce

Comment 4 caulier.gilles 2012-06-10 21:02:56 UTC

Same for me with 2.6.0

Gilles Caulier

Comment 5 caulier.gilles 2013-12-14 22:34:20 UTC

Danni Coy,

Can you give us a fresh update about this entry, using last digiKam 3.5.0 ?

Gilles Caulier

Comment 6 caulier.gilles 2014-08-30 22:15:54 UTC

Danni,

We need a fresh feedback here using last digiKam 4.2.0...

Gilles Caulier

Comment 7 caulier.gilles 2015-06-28 09:39:39 UTC

New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier

Comment 8 Bruno Randolf 2015-07-15 11:52:40 UTC

It works correctly now. Thanks!