[Kde-imaging] [Bug 151346] Kipi Time Adjust change the wrong date, should be configurable

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=151346


Marcel Wiesweg <marcel.wiesweg at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marcel.wiesweg at gmx.de




--- Comment #4 from Marcel Wiesweg <marcel wiesweg gmx de>  2009-08-07 10:59:03 ---
Jarle:

The original date and the digitization date take precedence over the "normal"
date when reading the creation date. Indeed, there should be an option

Karol:
Thanks for your contribution.

Some remarks on this patch:

- please use the "-U 2" formet if you create a patch with diff
- a kipi plugin can work with other apps not only digikam, so dont use in
"digikam internal" as description. It's the official "creation date" or
similar. It's really not an internal value but this is defined as the one and
true (per definition) creation date in the current application.
- Exif.Image.DateTime is (taken from libexiv2) "The date and time of image
creation. In Exif standard, it is the date and time the file was changed.". I
wouldn't call it Exif modification date (we read the creation date from it)
- have you tested starting the plugin with 1000 images? Is it ensured that we
dont read 1000 files' metadata then?

Generally, I'll wait for Gilles' (on holidays currently) approval on this.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.