| Summary: | After deleting images, the following item is not at top in the view. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Roland <carbonwerkes> |
| Component: | Albums-MainView | Assignee: | 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: | https://invent.kde.org/graphics/digikam/-/commit/52f8559c70a42eb29c2ee9d3a8a4c2c286645722 | Version Fixed/Implemented In: | 8.4.0 |
| Sentry Crash Report: | |||
|
Description
Roland
2024-06-30 16:10:25 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 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 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 |