issue with time stamp image created with digikam editor

[leoutation at gmx.fr]

On 1/29/24 18:56, Maik Qualmann wrote:
> Hmm, that's a matter of opinion. Cropping does not create a new image; it is a
> derivative of the original.

I know most people need to crop their images because composition don't
satisfy them, this is not my case.
In art/photography world, "cropping" is used to change
composition/framing, to create new images. It may totally change image
sense that has nothing to do with original image. This is my case.
Cropping date is needed, otherwise, i get problems when sorting these
new images.

> 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.
May be an option  to timestamp cropping ?

> 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