[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





--- Comment #7 from Marcel Wiesweg <marcel wiesweg gmx de>  2009-08-07 17:55:44 ---

> - "digiKam internal": the name digiKam is read by
> KGlobal::mainComponent().aboutData()->programName()

all right

> so other applications should show their own name. Anyway what this timestamp
> really refers to, is the KIPI::ImageInfo timestamp. So please suggest a better
> name for it if you don't like the "<application> internal".

"<Application> Timestamp"; "<Application> File Date"; "Timestamp from
<Application>"; "Date from <Application>"?

> 
> - EXIF modification: Is the problem only in the name, or do you want to have it
> bound with the file modification time? I treat it as an independent timestamp
> now.

No, only the name! E.g. in the Metadata Edit KIPI plugin, the three dates are
labeled "Creation date and time", "Original date and time", Digitization date
and time". Although the spec suggests differently, Exif.Image.DateTime is more
a creation date than a modification date.

> 
> - 100 files: to be honest I did not test with so many files (I will do that),
> but anyway the metadata are only read if you select the particular metadata as
> the source for your timestamps. In that case they should be read, so that you
> can see in the Examples how many of them are available and how many are
> missing.

ok. Just wanted to bring your attention to this. I sometimes like to test with
30,000 images ;-) (not editing, just opening the dialog).

Thanks very much, your contribution is highly appreciated.

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