Bug 365907 - digikam timestamp not updated after use of Adjust Time
Summary: digikam timestamp not updated after use of Adjust Time
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-TimeAdjust (show other bugs)
Version: 5.0.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-20 18:11 UTC by Kristian
Modified: 2018-09-22 08:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0
Sentry Crash Report:


Attachments
Example image before use of Adjust Time (98.45 KB, image/png)
2016-07-20 18:12 UTC, Kristian
Details
Example image in BQM with settings (129.11 KB, image/png)
2016-07-20 18:12 UTC, Kristian
Details
Example image after use of Adjust Time (original), details (102.43 KB, image/png)
2016-07-20 18:14 UTC, Kristian
Details
Example image after use of Adjust Time (copy), details (102.46 KB, image/png)
2016-07-20 18:14 UTC, Kristian
Details
Example image after use of Adjust Time (original), EXIF data (83.75 KB, image/png)
2016-07-20 18:14 UTC, Kristian
Details
Example image after use of Adjust Time (copy), EXIF data (88.24 KB, image/png)
2016-07-20 18:15 UTC, Kristian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kristian 2016-07-20 18:11:09 UTC
The digikam time stamps are not updated after use of Adjust Time tool. Only EXIF tags are updated. See screenshots.

Furthermore, the images are copied and not edited: Different behaviour to digikam 4

Reproducible: Always

Steps to Reproduce:
1. Choose images and add to BQM
2. Add Adjust Time tool and configure it e.g. +1 hour.
3. Images are copied, EXIF tags updated, 

Actual Results:  
Images are copied , digikam time stamp not updated.

Expected Results:  
Images are updated with changed times.
Comment 1 Kristian 2016-07-20 18:12:02 UTC
Created attachment 100209 [details]
Example image before use of Adjust Time
Comment 2 Kristian 2016-07-20 18:12:29 UTC
Created attachment 100210 [details]
Example image in BQM with settings
Comment 3 Kristian 2016-07-20 18:14:00 UTC
Created attachment 100211 [details]
Example image after use of Adjust Time (original), details
Comment 4 Kristian 2016-07-20 18:14:22 UTC
Created attachment 100212 [details]
Example image after use of Adjust Time (copy), details
Comment 5 Kristian 2016-07-20 18:14:56 UTC
Created attachment 100213 [details]
Example image after use of Adjust Time (original), EXIF data
Comment 6 Kristian 2016-07-20 18:15:24 UTC
Created attachment 100214 [details]
Example image after use of Adjust Time (copy), EXIF data
Comment 7 Maik Qualmann 2016-07-20 19:21:31 UTC
Whether a copy is made or whether the original file is overwritten, can be set under Behavior. A complete workflow can be saved with all settings and can be used repeatedly.

Maik
Comment 8 Kristian 2016-07-20 19:32:35 UTC
You're right, thank you for clarification. Which makes me point over to bug 365876. I think, the new behaviour with the BQM is absolutely not user-friendly.
Comment 9 Maik Qualmann 2016-07-24 05:08:46 UTC
Git commit cd9715c1a73b72f6fb3cec100cfb7d7d9f359722 by Maik Qualmann.
Committed on 23/07/2016 at 20:57.
Pushed by mqualmann into branch 'master'.

prevent locked database, and new file info in BQM is up to date
FIXED-IN: 5.1.0

M  +2    -1    NEWS
M  +14   -5    utilities/queuemanager/manager/task.cpp

http://commits.kde.org/digikam/cd9715c1a73b72f6fb3cec100cfb7d7d9f359722
Comment 10 Maik Qualmann 2016-08-05 18:58:33 UTC
*** Bug 366450 has been marked as a duplicate of this bug. ***