On 19 Jan., 20:49, "T. Modes" <[email protected]> wrote: > Hi Kay, > > On 19 Jan., 09:32, kfj <[email protected]> wrote: > > > This may work, but is > > it necessary? Until then, as posted previously, use the getVar() > > method as a workaround. > > Yes, it is necessary. The workaround works only for some variables > like yaw, pitch and so on. But with this I don't get e.g. the > projection or the crop region of the image, just to name some of the > also. Also without the macros I can not access the information about > linked variables (isLinked/isLinkedWith) in python.
Okay. Can you please point out where the lazy metaprogramming - so, the multiple inclusion of SrcPanoImage.h which instantiates the getXXX macros etc. with different variables - is happening? Or am I maybe misunderstanding the mechanism? - in which case please clarify how the accessor functions come to be. Then I can try and emulate the process in the interface definition file and make it generate the accessor functions. Now that the first step is done and the branch is established in the SF repo, I can start looking at details. Sory for having ben sloppy - I should have noticed the omission earlier. Blame it on my inexperience with the hugin body of code. 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
