issue with time stamp image created with digikam editor

[Sveinn í Felli]

My take on this is that the original image timestamp refers to the image 
subject; cropping (or other modifications) is just some work on that 
image subject, and should change the modification timestamp. And since 
we can shift in two clicks over to order by modification date/time, I 
don't see any necessity for changing current behavior.

Sveinn í Felli


Þann 29.1.2024 17:56, skrifaði Maik Qualmann:
> Hmm, that's a matter of opinion. Cropping does not create a new image; it is a
> derivative of the original. If we changed this, I know we would get bug
> reports from users who sort their images by date and now the changed image
> doesn't appear next to the other. What we could update would be a modification
> date. Let's see what other users think in this thread.
> 
> Maik
> 
> Am Montag, 29. Januar 2024, 17:56:42 CET schrieb leoutation at gmx.fr:
>> Hi
>> Here is the problem:
>> I crop image "A" to get new/different image "B".  I see this
>> new/different image "B" keeps same original image "A" time stamp even
>> though "B" is a new/different image. Time stamp should be new image
>> creation date, not old original image.
>> Is it a bug or a feature?
>> Conditions:
>> digikam git version
>> external mysql db
>> xmp metadata
>> digikam settings:
>> - Metadata -> behavior -> only "image tags" checked
>> - Sidecars  -> write to sidecar file
>>                  -> write to item and XMP sidecars
>>
>> --
>> Maderios
> 
> 
> 
>