[Digikam-devel] [Bug 151552] Album and Imageeditor cache problems

[Gilles Caulier]

http://bugs.kde.org/show_bug.cgi?id=151552


Gilles Caulier caulier gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ahuggel at gmx.net




--- Comment #18 from Gilles Caulier <caulier gilles gmail com>  2009-01-12 18:47:30 ---
Marcel,

In first, you talking about preview image (JPEG) saved in IPTC, not Exif
thumbnail. digiKam never use Exif thumbnail to render thumb in icon view.

I know this problem. i remember to have already see it with KDE3 code...

I have already hacking indeep but without sucess. All sound fine in code.

What's i' sure : when editor has transformed an image, IPTC preview is
recomputed when save files is called. The new preview image is a scaled version
using QImage:

http://lxr.kde.org/source/extragear/graphics/digikam/utilities/imageeditor/canvas/dimginterface.cpp#622

If you save this QImage to a dumy png file, you will see that preview is fine.
Preview is passed to DMetadata container and IPTC byte array containing preview
to DImg object.

Later, PNGLoader is called by DImg to save really image to file. Here, there is
2 way :

Exiv2 < 0.18 => PNG iptc byte array is saved using libPNG, thrue PNGLoader
code.
Exiv2 >= 0.18 = PNG iptc byte array is saved by Exiv2 since i have added PNG
writting mode in library.

I have never tested if this problem still exists with Exiv2 >= 0.18, but in
both case iptc must be written in PNG.

If i remember my investiguations, iptc data (outside IPTC preview) are written
and updated in iptc, but preview sometime failed to be updated to iptc byte
array.

For me, it's sound like a bug in Exiv2, but i'm not sure. After
investiguations, i cannot see where the problem can be in libkexiv2.

Gilles Caulier

PS: Andreas, i CC you for info...


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