https://bugs.kde.org/show_bug.cgi?id=490484
--- Comment #73 from Roberto <betoke...@gmail.com> --- (In reply to Maik Qualmann from comment #71) > Git commit 15101d696baf5491abb60be9013fadf3b5dd0b3c by Maik Qualmann. > Committed on 28/07/2024 at 09:03. > Pushed by mqualmann into branch 'master'. > > Revert "do not rescan item after writing metadata" > Related: bug 490821 > > M +2 -2 core/libs/database/engine/dbenginebackend.cpp > M +14 -3 core/libs/database/utils/ifaces/itemgps.cpp > M +20 -3 core/libs/fileactionmanager/fileworkeriface.cpp > M +2 -1 core/libs/properties/captions/itemdescedittab.cpp > M +2 -1 core/libs/tags/engine/tagmodificationhelper.cpp > M +8 -1 core/libs/threads/actionthreadbase.cpp > M +7 -3 core/utilities/facemanagement/database/faceutils.cpp > M +2 -1 core/utilities/imageeditor/main/imagewindow.cpp > M +3 -1 > core/utilities/maintenance/tools/autotags/autotagsassignmenttask.cpp > M +3 -1 core/utilities/maintenance/tools/imgqsort/imagequalitytask.cpp > M +3 -1 > core/utilities/maintenance/tools/metaremover/metadataremovetask.cpp > M +5 -2 core/utilities/maintenance/tools/metasync/metadatasynctask.cpp > M +3 -1 core/utilities/queuemanager/manager/actionthread.cpp > > https://invent.kde.org/graphics/digikam/-/commit/ > 15101d696baf5491abb60be9013fadf3b5dd0b3c So, rescanning item after writing metadata *is* necessary? Could you elaborate a bit why? There is a metadata setting "Rescan file when files are modified" which I thought would control rescanning or not... /Roberto -- You are receiving this mail because: You are watching all bug changes.
