https://bugs.kde.org/show_bug.cgi?id=437897
Quincy <bbc.qui...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
--- Comment #12 from Quincy <bbc.qui...@gmx.de> ---
Further remarks on the Windows situation:
- I replaced the test file as the small one did not work as described (Maik
found out by himself).
Using Linux (with digiKam 7.1 in that case) I see the following behavior:
- Copying updates the creation timestamp and leaves modification with its old
value (as on Windows)
- Rotating the image file does not update creation or modification timestamp at
all (in contrast to Windows)
So my summary (also answering your earlier question): We should distinguish
between database and file properties:
- Given the situation that Windows as well as Linux always update creation time
when copying files (without changing content) and do not update the
modification time IMHO its more useful to prefer modification time over
creation time for reading the content of ImageInformation.creationDate (as the
content was "created" in the state which is read into dK at modification time).
- When rotating the image, content is changed, so an update of file's as well
as database modification time makes sense (it's not the very same unmodified
file as before), but ImageInformation.creationDate should stay the same (as
would an Exiv tag if it existed).
--
You are receiving this mail because:
You are watching all bug changes.
