kfj> That's how I did it. In a beginning-of-line context accept all kfj> conventional line-headers plus the 'meaningful comment' type as legal kfj> line-type tokens. This seems to be the least painful route. Luckily kfj> line beginnings like '# hugin' don't seem to contain meaning but only kfj> serve as comments. The only slightly annoying part is that these kfj> additional line types have a slightly different syntax, insofar as kfj> some use <key>=<value> syntax, like
kfj> #-hugin cropFactor=1 kfj> and others merely give a field value without a field header like kfj> #hugin_optimizeReferenceImage 0 in PToptimizer the rules can be: var<value> or var=<value> Each has a different meaning (first is assignment, the second is a reference to another image). --dmg kfj> so there are different parsing rules needed for the additional types. -- -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
