hugin-devs team mailing list archive
-
hugin-devs team
-
Mailing list archive
-
Message #02121
[Bug 799905] Re: Variables not passed to Python interface
I managed to get the code to work properly by doing this:
In .../src/hugin_script_interface/hpi_classes.cpp (line 130) is the call
to SWIG_Python_TypeQuery. Take away the SWIGRUNTIME before the
statement, so that it reads:
swig_type_info* swigtype = SWIG_Python_TypeQuery ( hsi_type );
I attach a patch that does this modification; it's made by hg diff.
I mistook the SWIGRUNTIME for part of the return type specification,
which it obviously isn't.
Kay
** Attachment added: "this fixed the bug on my system"
https://bugs.launchpad.net/hugin/+bug/799905/+attachment/2177754/+files/patch_hpi_classes
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/799905
Title:
Variables not passed to Python interface
Status in Hugin - Panorama Tools GUI:
Confirmed
Bug description:
Trying to pass several variables to Python script does not work.
I'm calling hpi::callhpi with 2 argument
hpi::callhpi( m_scriptFile.c_str() , 2 , "HuginBase::Panorama*", &pano, "HuginBase::UIntSet*", &m_images ) ;
But in hpi_dispatch 2 HuginBase::Panorama* objects appear (and not a Panorama and UIntSet object)
I added
for i in args:
print(type(i))
to hpi_dispatch and got:
<class 'hsi.Panorama'>
<class 'hsi.Panorama'>
as result.
And finally in the plugin only the first Panorama object appears.
I added the same code as above to check, there is only one variable in def entry (pano,*args)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/799905/+subscriptions
References