[KPhotoAlbum] Is this supposed to happen?

[Robert Krawitz]

On Sat, 20 May 2017 23:54:16 +0200, Johannes Zarl-Zierl wrote:
> On Samstag, 20. Mai 2017 14:13:58 CEST Robert Krawitz wrote:
>> I've found two images in a file that have the same stack ID but
>> different ordering.  I thought that that wasn't supposed to happen?
>> 
>>         <image file="pano/barharbor30/img_9151.cr2" label="img_9151"
>> startDate="2013-06-09T19:29:17" endDate="2013-06-09T19:29:17" angle="0"
>> md5sum="537fad17b53198d1695fa6905931fb40" width="5184" height="3456"
>> stackId="17071" stackOrder="3"/> <image
>> file="pano/barharbor30/img_9151.jpg" label="img_9151"
>> startDate="2013-06-09T19:29:17" endDate="2013-06-09T19:29:17" angle="0"
>> md5sum="6e099d4b0972fcc09ee3f8f77d76a23e" width="5184" height="3456"
>> stackId="17071" stackOrder="3"/>
>
> This is not supposed to happen.
>
> Yet, I find the same problem in my database:
>
> grep stackId index.xml | \
>  sed 's/.*stackId="\([0-9]*\)".*stackOrder="\([0-9]*\)".*/stack \1 idx \2/' |\
>  sort | uniq -d
> stack 12 idx 1
> stack 77 idx 1
> stack 77 idx 3

So at least one of the problems is real :-)

My script does clean that particular problem up.
-- 
Robert Krawitz                                     <rlk at alum.mit.edu>

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --    http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton