[Digikam-users] Digikam rotation

[Peter Albrecht]

Hello Anatoly,

regarding "non-destructive":
The jpeg rotation is "loss-less". This means the jpeg is not
decoded rotated and then encoded again, which would result
in quality loss, but rotated in encoded state.

But these changes are written to the file again. So the file
needs to be touched. It looks like something went wrong with
aborting this action.

I agree, that aborting the action should not destroy the
file. But I know to little about digikam internals, to tell
more.

Regards,
	Peter Albrecht

On 14.08.2012 23:53, Anatoly Burakov wrote:
> Hi all
> 
> I've just encountered a very strange behaviour. I was selecting pictures to 
> move to another albums, and my touchpad had accidentally kicked off the 
> scroller (the laptop is old, false scrolls happen fairly regularly). Digikam 
> started to batch rotate images. Of course, since there was quite a few images 
> selected and i didn't want all of them to be rotated, i've pressed Abort on 
> each image. However, digiKam destroyed most of the images after i did that. By 
> destroyed i mean some of them are half greyed out (you know, when image is 
> incomplete), some of them became empty 0B sized files etc.
> 
> How does this even happen? Aren't all the actions supposed to be non-
> destructive? Why did it kill my images?
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users
>