digikam default options

[cerp]

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.

Best,


Quoting Simon Frei <freisim93 at gmail.com>:

> Hi Corrado & Rina,
>
> This option is available in configuration at Metadata -> Behavior ->
> Reading and Writing Metadata -> Update file timestamp when files are
> modified.
>
> Cheers,
> Simon
>
> On 14/01/17 14:50, cerp wrote:
>> Dear all,
>>
>> This is exactly the second problem we have: when you modify the exif
>> data of the JPG or RAW fle, for example for adding copyright
>> information, or photograph title and description (important for some
>> assignment and for some contests / prizes), the file timestamp is
>> modified, which means the whole time order is screwed and when you
>> then try to open the photographs with another editor or DAM tool.
>> Would it be possible to have the option to switch off modification of
>> the file timestamp when we only modify the exif data?
>>
>> Best Regards
>>
>> Corrado & Rina
>>
>>
>>
>>
>>
>> Quoting Remco Viëtor <remco.vietor at wanadoo.fr>:
>>
>>> On samedi 14 janvier 2017 13:55:04 CET Gilles Caulier wrote:
>>>> 2017-01-14 13:51 GMT+01:00 Remco Viëtor <remco.vietor at wanadoo.fr>:
>>>>> On jeudi 12 janvier 2017 08:49:06 CET Andrey Goreev wrote:
>>>>> > Hello,
>>>>> >
>>>>> > I thought it might be not a bad idea to let users
>>>> activate/deactivate
>>>>> > the
>>>>> > following options during the initial setup wizard:
>>>>> >
>>>>> > * Update file timestamp when files are modified (activated by
>>>> default)
>>>>> > * Always show original images (deactivated by default)
>>>>> >
>>>>> > I have a feeling that many users would prefer to have updating
>>>> the file
>>>>> > timestamp box unchecked and show original images checked.
>>>>>
>>>>> Showing original images as default: yes; that avoids images
>>>> appearing as
>>>>> 'not
>>>>> present' and considered 'lost' (see mailing list...)
>>>>>
>>>>> NOT updating timestamps as default: no, for at least one simple
>>>> reason.
>>>>> If you mean the file "last-modified" timestamp, not updating that
>>>> would
>>>>> break
>>>>> all "make-like" programs and scripts, that use that timestamp to
>>>> see if a
>>>>> particular fiel needs treatment?
>>>>
>>>> Ah i miss-understand your previous mail. The option is enabled by
>>>> default
>>>> and your want to see this option turned off now. Right ?
>>>>
>>>> Gilles Caulier
>>>
>>> It's my first mail in this thread, so, "which previous mail"? :^)
>>> My reply was to Andrey Goreev (the OP)
>>>
>>> For the record, I agree with what you stated as Digikam defaults in your
>>> earlier mail (Sat, 14 Jan 2017 11:10:12 +0000 (UTC)):
>>> Update file timestamps          : YES
>>> Always show original images : YES
>>
>>
>>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170114/5425165e/attachment.ksh>