On 20 Jan., 18:54, "T. Modes" <[email protected]> wrote:
> Hi Kay,
>
> continue the accessor issue mentioned in the other thread.
>
> The accessor functions are defined in SrcPanoImage.h, lines 117 - 172
> by using macros and inclusion of image_variables.h multiple times.

Thanks. I'm working on the issue, and I must say I'm having a hard
time - the code is quite intransparent. But I hope I'll manage to have
the accessors soon. I'll keep you all posted. It would help if I had a
technical outline of how and where precisely they are made, but maybe
I'll manage with a bit of intelligent guesswork...

> PS: hsi and hpi compiles on windows.

great.

> Importing the python lib works
> also. But when running a script inside hugin it return value is always
> -2 and the script is not executed. Ideas?

Try and run hugin from the command line and see what the python
interface says why it fails. Most likely it can't load the modules hpi
and hsi because they're not in the module path. Remember hpi.py is not
output, but handcoded and therefore lives in the hsi directory
initially - if you want all the files in one place, copy it over to
where hsi.py and _hsi.so (or whatever they're called on Windows) live
in the target directory (like, hugin.hg-build/src/hsi). I haven't yet
figured out how to tell CMake that something is just there and doesn't
have to be generated from somewhere. The code where the error
originates is in hpi.cpp. try:

export PYTHONPATH=<whatever directory your hsi.py _hsi.so and hpi.py
are in>
<path to hpi-linked hugin>/hugin

I have also put more up-to-date documentation in README.hsi in the hsi
directory, if you need to read up on what does what, but of course I'm
always happy to help here.

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

Reply via email to