On 2 Jan., 15:37, Yuval Levy <[email protected]> wrote:
> currently a CP line in the PTO file looks like:
>
> c n0 N1 x2319.75430140533 y1306.89102657256 X635.409481924115
> Y1295.02701452379 t0
>
> what would it take to expand it to:
>
> c n0 N1 x2319.75430140533 y1306.89102657256 X635.409481924115
> Y1295.02701452379 t0 s0 a0 w100
Just a quick answer to this one: my Python pto parser would accept it,
but the C parser used by hugin would probably throw a fit, so you'd
have to change code in there. But there is another way. It's what I
call an 'ugly duckling' in my python pto parser: you could introduce a
line in the guise of a comment, preceding the CP line, looking like
#-hugin cpWeight s0 a0 w100
AFAIK this is established practice for introducing additional
('noncritical') values into the pto without breaking compatibility
with other pto-using programs.
Kay
--
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
