https://bugs.kde.org/show_bug.cgi?id=142753Jens B. Benecke <
[hidden email]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jens-bugs.kde.org@spamfreem
| |ail.de
--- Comment #3 from Jens B. Benecke <
[hidden email]> ---
Would it be feasible to allow undo of such operations (editing metadata) if and
only if direct modification of image files is disabled? The implementation
could maintain an "undo" database table where a SQL string is stored for each
operation that would undo exactly that operation. (Or a more structural
approach, storing the type of operation including previous values).
If sidecar files are used, a backup file could be created upon modification.
I am also sorely missing undo for image modification in Digikam and I would be
content with fiving up direct image file modification.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
