Page 2 of 2

Re: export snapshot at DPI

Posted: Mon Sep 22, 2014 8:33 am
by LCMark
@monte: Hello :)

Let me see if I can answer your questions...

1) It seems unlikely that fractional dots-per-inch values would be useful, so I suggest using round-to-nearest ( floor(v + 0.5) ) for that value imported into LC.
2) The array properties section controls whether 'the value[key]' syntax works - if a property is not in that range then you can't directly access keys of the array using 'the' syntax. I'll have to check with @runrevali, but I believe this has all been unified in 7.0, so it doesn't really matter at the moment.
3) This is a good point - I think it would be better to document separately - maybe 'metadata_of_field.xml'?

Re: export snapshot at DPI

Posted: Tue Sep 23, 2014 12:06 am
by monte
OK

For 3 do you want me to change the current metadata.xml to metadata_of_field.xml and then add a new metadata_of_image.xml? or just add the metadata_of_image file? I'm not sure how these things are indexed.

Re: export snapshot at DPI

Posted: Tue Sep 23, 2014 1:44 pm
by livecodeali
Hi Monte,
I have just pushed a fix to the refactor branch so that it doesn't care anymore if array properties are in that range of the enum. That should sort out any problems there.

Re: export snapshot at DPI

Posted: Tue Sep 23, 2014 2:48 pm
by LCMark
@monte: I think renaming them both makes sense - it makes it clear then in the filename what the entry is for. I believe the dictionary is indexed based on the content of the XML files, rather than their filename.

Re: export snapshot at DPI

Posted: Wed Sep 24, 2014 12:28 am
by monte
OK, thanks

Re: export snapshot at DPI

Posted: Thu Sep 25, 2014 4:49 am
by monte