https://bugs.kde.org/show_bug.cgi?id=489501
--- Comment #2 from Roland <carbonwer...@hotmail.com> --- 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 -- You are receiving this mail because: You are watching all bug changes.
