digikam default options
Andrey Goreev
aegoreev at gmail.com
Sat Jan 14 15:44:09 GMT 2017
Cerp
I think Linux does not save "date created" for files on only keeps "date modified" instead. So if you are using Linux and updated file stamps you lost chronological order in the file browser (nautilus, etc.) Windows keeps both "date created" and "date modified" as well as its file explorer allows users to sort files by any date including exif date taken.So if you are a Linux user you get harmed by digikam for not going through all the options in the beginning. You can fix the dates using exiftool (exiv2 will probably do that too) but that's at least 30 min of your life you will never get back.
Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: cerp <cerp at eeos.biz> Date: 2017-01-14 8:25 AM (GMT-07:00) To: Remco Viëtor <remco.vietor at wanadoo.fr> Cc: digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users at kde.org> Subject: Re: digikam default options
It is digikam that changes the timestamp, not the filesystem. I do not
understand your point.
Best,
Quoting Remco Viëtor <remco.vietor at wanadoo.fr>:
> On samedi 14 janvier 2017 16:01:34 CET cerp wrote:
>> Dear Simon,
>>
>> In our case it is unflagged, but digikam still changes the timestamp
>> of the file (in the filesystem on the disk) .... which means when you
>> open with a filemanager or a different DAM tool the picture order is
>> completely screwed.
>
> I'm not sure Digikam has anything to say in that decision.
> File saving is handed off to a driver in the system (rather evident, once you
> realise how many file systems exists: Linux has at least 5 that it
> can handle:
> BTFRS, Ext4, NFS, Fat, NTFS; there are probably more that I've never seen/
> used. Afaik, it's the driver that as a matter of course adjusts the time
> stamps in the file system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170114/2c6b16c4/attachment.html>
More information about the Digikam-users
mailing list