On 4 Feb., 00:19, Bruno Postle <[email protected]> wrote: > On Thu 03-Feb-2011 at 13:45 +0900, Daniel M. German wrote: > > >No. These ones surprised me. There are already 3 types of "hugin" > >variables. if libpano was a mess, hugin is helping: > > They are all comments, so you can ignore them when stitching or > optimising. They do carry information used by the GUI.
That would imply that the GUI later on has to look at the pto again to find those 'comments that carry information used by the GUI'. Wouldn't it be the point to have a single parser for all pto that it also supplies these data in an internal representation? Other software would be free to ignore it, but having to reparse the pto to extract some more data sems silly. 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
