Version: 2.0.0 (using KDE 4.6.2) OS: Linux when I save an image with the "new version" option after having it edited in the editor, it is placed at the end of the thumbnail list which I have placed on the left side, and the image editor also points to that image. So I have to scroll back to the place, where the next image is that I want to edit. In a long list of images, this is very tiresome. This behaviour was there in the 1.9 version as well, but there I could move to the really next image with the arrow-icons for next or previous image. Now it just goes back one image when I click there, which is the before-last one. I help myself by closing the editor each time and opening it up again for the next image which I chose from the album view of digikam, but I think that's no good behaviour. Did I miss some adjustment? Or is this a bug? Reproducible: Always Steps to Reproduce: Open image editor change the image select new version from the toolbar let it save the file Actual Results: as said, the image is placed within the thumbnail list at the bottom, even though the original (with the same name except for the _v#-ending) is placed somewhere in the middle of the list. Expected Results: The image should be placed in the expected order, which is by filename, and appear next to the image that has been edited. No idea.
Git commit a3d36f4c4aaea7b7938482fae7e7587097ad7780 by Marcel Wiesweg. Committed on 10/09/2011 at 16:50. Pushed by mwiesweg into branch 'master'. Ensure the sortfilter model in ImageWindow actually filters New entries should now be sorted according to the main view's sort order BUG: 280540 M +1 -0 utilities/imageeditor/editor/imagewindow.cpp http://commits.kde.org/digikam/a3d36f4c4aaea7b7938482fae7e7587097ad7780
I opened the following bug earlier, which is very likely the same : https://bugs.kde.org/show_bug.cgi?id=277585 Maybe it should be closed as duplicate...
*** Bug 277585 has been marked as a duplicate of this bug. ***
I just installed version 2.1.0 of Digikam and found the same behaviour as initally reported. For which version is the status "RESOLVED" or the resolution "FIXED" meant? Do I read something on this page the wrong way?
current implementation fro git master (next 2.2.0 release) Gilles Caulier