https://bugs.kde.org/show_bug.cgi?id=489501
Bug ID: 489501
Summary: Delete of group of photos in an album leaves the index
at the offset value of the number of the next photo in
sequence, vs the actual next photo once those deleted
files are culled.
Classification: Applications
Product: digikam
Version: 8.4.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: digikam-bugs-n...@kde.org
Reporter: carbonwer...@hotmail.com
Target Milestone: ---
***
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
--
You are receiving this mail because:
You are watching all bug changes.
