Bug 277585 - When using "Save as new version", the new file is added at the end of the thumbbar
Summary: When using "Save as new version", the new file is added at the end of the thu...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: ImageEditor-Versioning (show other bugs)
Version: 2.0.0
Platform: Compiled Sources Linux
: NOR minor
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-11 21:20 UTC by Frederic Grelot
Modified: 2022-02-02 05:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 6.3.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frederic Grelot 2011-07-11 21:20:23 UTC
Version:           2.0.0 (using KDE 4.6.4) 
OS:                Linux

when in the editor, when I make changes to an image, and use "Save as new version", I expect the new version to appear right after the original in the thumbbar (as is does in the album view actually). Instead of that, the new version appears at the very end of the thumbbar and, the list gets scrolled to it, which forces me to scroll back to my previous position.
The only way to have it where it should is by closing and reopening the editor

Reproducible: Always

Steps to Reproduce:
Steps to Reproduce:
-Open an image in editor view
-activate the "Thumbbar"
-modify your image in any way
-press "Save as new version"

Actual Results:  
The new image file appears at the very end of the list, gets selected, and the scroll bar goes there

Expected Results:  
The new image should appear right after the original, get selected, and the scroll bar should eventually scroll to it (in case it is outside the view)

OS: Linux (x86_64) release 2.6.38.8-32.fc15.x86_64
Compiler: gcc
Version : 2.0.0-git_ecf6e3fe0fcbebaea75e6be8ad33e66199564241
Personal opinion : digikam is great! :-)
Comment 1 Marcel Wiesweg 2011-09-11 13:44:12 UTC

*** This bug has been marked as a duplicate of bug 280540 ***
Comment 2 caulier.gilles 2019-08-13 20:57:38 UTC
Fixed with bug #280540