digikam default options

[Simon Frei]

I can only repeat myself:

    There is clearly a misconception here:

    The "Date modified", "mtime" or whatever it is called property is
    NOT the time a picture was taken. That information is stored in the
    file itself, in the exif header. So the moment of your capture does
    not change at all unless you specifically do so using tools to
    modify the exif header of the file. 

There is no harm in updating the modified time/mtime. This is not part
of the file, it is a property of the file in the filesystem. It has
NOTHING AT ALL to do with time you captured your image. It is used for
stuff like backuping, syncing, ...
So please change the option if you must (it is not a good idea as you
don't seem to understand it), but the standard behaviour is correct.

On 14/01/17 16:38, Andrey Goreev wrote:
> I don't agree. Any options that can "harm" an inattentive user. Any
> date changes are a harm.
> For example, I installed digikam and imported my pictures. Some of
> them went to Miscellaneous / Places / zoo instead of Places / zoo. For
> sure I changed it right away but I was not aware of that timestamp
> update option being turned on and changed the date of 300+ files.
> For sure it might be considered as a user issue but again, I think
> user should be protected. Let's at least allow users to turn that
> option on/off in the initial setup wizard.
>
>
> Sent from my Samsung Galaxy smartphone.
>
> -------- Original message --------
> From: Remco Viëtor <remco.vietor at wanadoo.fr>
> Date: 2017-01-14 8:11 AM (GMT-07:00)
> To: digiKam - Home Manage your photographs as a professional with the
> power of open source <digikam-users at kde.org>
> Subject: Re: digikam default options
>
> On samedi 14 janvier 2017 07:30:08 CET Andrey Goreev wrote:
> > Well, I take pictures to capture moments. So why should the date of the
> > moment be changed if I simply added an info in order to be able to find
> > that picture later ?
>
> There is a tag reflecting the time the image was taken. That one is
> not (and
> should not be) modified on any update, afaik.
>
> Also, we were talking about the best default for a configuration
> option. If
> you do not like the default, you can change it.
>
> But for me, a timestamp that's supposed to record the date/time an
> image was
> changed should _as_a_default_ do exactly that, to avoid surprising (new)
> users.
>
> Remco.
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170114/562b13a1/attachment.html>