[KimDaBa] Ouch! (data loss)

[Jesper K. Pedersen]

On Monday 03 January 2005 09:29, Sam wrote:
| Hi,
|
| I presume it solve the problem described in this email:
| http://sulaco.hrhansen.dk/pipermail/kimdaba/2004-October/000702.html
I was never capable of reproducing this bug, but given that the code for 
sorting has been completely rewritten, there is a sensire home that is does.

|
| Le 02.01.2005 17:54, Robert L Krawitz :
| > This looks like the culprit.  Note that if the md5sum fails, it
| > doesn't restore the images.
| >
| >         //remove every item of sorted from the images_list(the main list)
| >         //because we add all the images from sorted afterwards
| >         //(we would have them doubled if we wouldn't remove them)
| >         for( ImageInfoListIterator it3( sorted );*it3; ++it3 ) {
| >             if (!(images.removeRef((*it3)))){
| >                 KMessageBox::error(0,i18n("MD5Sum failure; try recalcing
| > your MD5Sums.")); return;
| >             }
| >         }
| >
| >         //insert sorted block of images in place of block of unsorted
| > images // index represents the place of the first selected unsorted image
| > for( ImageInfoListIterator it4( sorted );*it4; ++it4,index++){
| > images.insert(index,(*it4));
| >         }
|
| _______________________________________________
| KimDaBa mailing list
| KimDaBa at klaralvdalens-datakonsult.se
| http://sulaco.hrhansen.dk/mailman/listinfo/kimdaba

-- 
Having trouble finding a given image in your collection containing
thousands of images?

http://ktown.kde.org/kimdaba might be the answer.