[Digikam-devel] [Bug 297804] Saving an image loses portait orientation

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=297804

--- Comment #11 from Marcel Wiesweg <marcel.wiesweg at gmx.de> ---
Anything touching the interpretation of the orientation field does not require
a schema update, but is nonetheless completely backwards incompatible. (means
you can't use your converted database with a prior version - we do this very
rarely, only every few years).

Setting a property when orientation is changed manually seems a possible
solution, but there's a drawback with files out there which were already
changed manually - a lot of rotation information would be lost suddenly if a
user did some unrelated editing.

You've seen the problems:
- we dont know if anything of the metadata was changed, we only see "the file"
was edited
- we dont store the user-edited rotation differently from the one read from the
file

Essentially, we treat rotation like all other metadata: Manual changes outside
digikam need to be applied by re-reading metadata from file to db. No question
that this tool should provide finer-grained control over which fields to read.

-- 
You are receiving this mail because:
You are the assignee for the bug.