What happened to the hsi?

[Kornel Benko]

 

Am I the only one missing the 'Actions' button in the main window?

 

I could not find any menu entry for WOA in recent created hugin.

Still, the plugins are installed.

 

Kornel

[Terry Duell]

Hello Kornel,

On Fri, 07 Feb 2014 22:01:43 +1100, Kornel Benko <Kornel...@berlin.de>
wrote:

>
> Am I the only one missing the 'Actions' button in the main window?
>

No sign of it here either, current default branch local Fedora build.

> I could not find any menu entry for WOA in recent created hugin.
> Still, the plugins are installed.

Likewise.


Cheers,
--
Regards,
Terry Duell

[Harry van der Wolf]

Hi,

this is an issue in the beta1. The max api is set to 2013 and should have been set to 2014 (I'm sorry.) However, due to changes in the new libpano, the woa plugin didn't function anymore. This has also been fixed.

The beta2 or RC1 shouldn't have this issue. I want to release it this weekend.

Harry

2014-02-08 Terry Duell <tdu...@iinet.net.au>:

--
Regards,
Terry Duell

--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/op.xax76dngrs0ygh%40localhost.
For more options, visit https://groups.google.com/groups/opt_out.

[Kornel Benko]

Ping, ping ...

 

It looks like hugin (default branch) is still missing the woa entries.

 

Kornel

 

Am Samstag, 8. Februar 2014 um 12:10:55, schrieb Harry van der Wolf <hvd...@gmail.com>

> > email to hugin-ptx+...@googlegroups.com.

[T. Modes]

Am Freitag, 14. Februar 2014 11:38:33 UTC+1 schrieb kornel:

Ping, ping ...

 

It looks like hugin (default branch) is still missing the woa entries.

pong, pong.

woa is still broken. So we can't update the entries. Not the first time

https://groups.google.com/d/msg/hugin-ptx/Mn8TTswU1Us/O7wHejOQO84J
https://groups.google.com/d/msg/hugin-ptx/A3sOp_RTWiY/zFoTOOHHkQ8J
https://groups.google.com/d/msg/hugin-ptx/fl4mQ0r7Op4/HAIQMEhVbEkJ

[Terry Duell]

On Sat, 08 Feb 2014 16:57:39 +1100, Terry Duell <tdu...@iinet.net.au>
wrote:

It has re-appeared in a recent build of the default branch
(6554:7ff646d5e247), and reported as back in the 2014.0.0 RC1.

[kfj]

I reckon the patch I sent in and which Kornel applied was only against the default branch, and that's why it did not make it into earlier forks. Two thing happened there:

- the api changed, breaking woa. This was easily fixed by adding code to make up for the variant of SrcPanoImage's constructor taking a filename as it's argument; the changed code is now in the default branch.

- @api-max in all plugins was not updated to the current API version, resulting in the plugins not being accepted as valid for the latest version, and since no valid plugins could be found, the 'Actions' menu did not show up.

My patch fixed the problems in the default branch, but the changes may have to be applied to other branches as well. The update of the @api-max (and sometimes @api-min) values  has to happen with every new version; this is apparently documented as part of the release process but has been forgotten occasionally.

The code changes to woa.py as applied in the default branch should be introduced into earlier versions if they use the new API with the missing SrcPanoImage constructor variant, I don't know when the API change was introduced. If they use the old API, the old woa.py code should be used. @api-min and @api-max must always be set appropriately.

Kay