hugin-devs team mailing list archive

[KFJ <1448816@xxxxxxxxxxxxxxxxxx>]

I'd look into the matter but in fact I am getting bored by this problem
reappearing every year. Yuv did at the time introduce the 'API check',
and ever since it hasn't produced anything useful, but one set of errors
every year. When once the API actually did change, the woa plugin simply
broke, and the 'API test' did nothing to prevent it. Apart from this one
time, any changes to the API that happened never broke the plugins
because they only use a small subset of the 'API', which is really just
the content of the headers the swig file processes to generate the
python interface. So I propose simply throwing out the API test. I
suppose I can live with a broken plugin every once in a while, and noone
apart from me has ever written another plugin anyway. If noone objects,
I'd be glad if someone else could throw out the relevant bit of code,
since I don't know where it is and I'd have to search from scratch -
alternatively a hint as where to find the code would be appreciated.

Kay

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1448816

Title:
  hugin-2015.0.0_beta1 has no 'Actions' menu

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  hugin-2015.0.0_beta1 builds here OK, but has no 'Actions' menu.
  I have built using rpmbuild on Fedora 21, using the same .spec file as for recent builds of the default branch and those builds provide the 'Actions' menu, although attempting to use WOA in a recent build of 2014.1.0 did return an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1448816/+subscriptions