[Digikam-devel] [Bug 220545] Cannot write XMP sidecar files

Gilles Caulier caulier.gilles at gmail.com
Wed Mar 23 10:18:36 GMT 2011


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





--- Comment #67 from Gilles Caulier <caulier gilles gmail com>  2011-03-23 11:18:34 ---
Marcel,

As you said in your comment #54, now metadata settings are handle in DMetadata
constructors.

https://bugs.kde.org/show_bug.cgi?id=220545#c54

To complete XMP sidecar support, it still a lead problem to solve : manage
image and sidecar files at the same in these cases :

1/ Image Editor : File Save/SaveAs : when temp image file is created, it's
moved move to target file path. XMP sidecar still in temp place. Code relevant
is there :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/utilities/imageeditor/editor/editorwindow.cpp#L2705

2/ Album GUI : When image files are moved, copied, renamed, deleted, sidecar
files must be managed with the same rules at the same time. Code relevant is in
DIO if i'm not too wrong :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/digikam/database/dio.cpp

3/ In BQM, when new file is created in a workflow, sidecar file must be managed
at the the time. A temp file is created as in editor, it's the same problem.
Code relevant is there :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/utilities/queuemanager/main/queuemgrwindow.cpp#L1116

4/ In CameraGUI, sidecar file must be managed during import. Code relevant is
there :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/utilities/cameragui/controller/cameracontroller.cpp#L870

5/ In kipi-plugins, all tools which create new files must manage sidecar
accordingly with digiKam metadata settings.

I hope to not forget another place where image files are managed like this...

Gilles Caulier

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list