Bug 489501

Summary: After deleting images, the following item is not at top in the view.
Product: [Applications] digikam Reporter: Roland <carbonwerkes>
Component: Albums-MainViewAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.4.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In: 8.4.0
Sentry Crash Report:

Description Roland 2024-06-30 16:10:25 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

Within an album, a delete of some number of photos (say, the first 100 of 1000) removes those 100, but indexes the viewer to image 100 of the remaining 900. This is a problem, where if you have imported a large number of photos (where these are often groups via photo sessions etc), and you want to cull files, you can end up skipping some number of files for review.


STEPS TO REPRODUCE
1. With an album that has some large number of photos (say, 1000), select perhaps the first 50
2. Hit the delete key
3. 

OBSERVED RESULT
The indexed/active photo is not the next photo in series- it is the next index offset (i.e. 51) of the remaining photos in the album

EXPECTED RESULT
System should reset index to the first of the remaining photos. There is never a case where you would want the index to point to some arbitrary offset, since this is about position in the list of files, not a process done to files selected that remain in place.

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2024-06-30 16:47:54 UTC
I don't have Windows available here at the moment. But I can't reproduce the problem here under Linux, the next active item is the one after the deleted ones.

Maik
Comment 2 Roland 2024-06-30 17:03:06 UTC
Im sorry, I wasnt at all clear. The physically active image index IS the next image that was shown in the view prior to the delete. The problem is that the view index is offset, so if you delete 100 files, the active index is the next in the list, but the view index is at 100 (you dont see the active item). So, if you assume you are looking at the next file in the catalog (which is how most file systems work- you delete the first 50 items, the system sets the next item in the index as in view), it is easy to accidentally delete or miss images not intended to be deleted or skipped.

Perhaps there is a config option that resets the album view to update to show the active image at position 1 in the view after a delete operation? 

Best
Rob
Comment 3 Maik Qualmann 2024-06-30 20:34:19 UTC
Git commit 52f8559c70a42eb29c2ee9d3a8a4c2c286645722 by Maik Qualmann.
Committed on 30/06/2024 at 20:33.
Pushed by mqualmann into branch 'master'.

scroll current item to the top of the view when deleting
FIXED-IN: 8.4.0

M  +1    -1    NEWS
M  +4    -0    core/libs/widgets/itemview/itemviewcategorized.cpp

https://invent.kde.org/graphics/digikam/-/commit/52f8559c70a42eb29c2ee9d3a8a4c2c286645722