On 27.04.2015 17:16, tmodes wrote: >> The .py modules mentioned shold be changed to have >> # @api-max 2015.0 >> instead of >> # @api-max 2014.1 > > I know. But it would be nice if someone could test the scripts and > report back if there are still running. (I never used them so I can not > judge if they are still okay.)
I can not judge, either. But api-max was set to 2014.1, so I assume that these scripts were activated in the development version. I'd expect that a breakage would have been noticed there. > > Currently it seems that woa is currently not running, so for woa we can > not update the api-max. Only when the issue is fixed we need to update > api-min *and* api-max for woa then. > If this is true, it seems that no one cared during the development cycle then. Wouldn't it be more honest to axe woa if nobody gives a damn? Regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford -- 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 _______________________________________________ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
