hugin-devs team mailing list archive

[tmodes <1369782@xxxxxxxxxxxxxxxxxx>]

This option is to specify a path to enblend when it is not at the default path or there are different versions of enblend (image cache, openmp,..)
It is not intended for alternative blenders, this is only a side effect. The options passed to the program are specific for enblend, other program does not understand it all.

You answer back in your points:
>Hugin should not worry about that field unless the box is checked. 
>and unchecking the box right away causes the field not to be saved. 

> The default arguments are universal, and not executable specific. They shouldn't be. 
> That way, new arguments don't have to be entered upon changing the checkbox.

No. You can also specify arguments for the default enblend program.

** Changed in: hugin
       Status: New => Invalid

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

Title:
  problems with "Programs" preference pane

Status in Hugin - Panorama Tools GUI:
  Invalid

Bug description:
  Hugin 2014 RC4 on a MacBook Pro running OS X 10.9.4

  The "Programs" preference pane is a bit confusing in the section on
  using alternatives to enblend (and enfuse).

  1. The text, I think, should be "Use alternative to enblend", rather
  than "Use alternative Enblend program", which implies that there might
  be another thing called enblend (which I don't think is what is
  intended, though perhaps I am wrong here).

  2. Checking the box allows for entry of another executable, yet the
  label to the right of that field says "enblend executable", which is
  confusing. Instead enblend should never have to be written there, and
  Hugin should not worry about that field unless the box is checked.
  (Obviously I have no idea whether it actually does check it, but the
  pane gives that appearance.)

  3. Checking the box and then putting in a new executable name and
  unchecking the box right away causes the field not to be saved. It
  should be. Closing prefs before unchecking does save the field.

  4. The default arguments are universal, and not executable specific.
  They shouldn't be. That way, new arguments don't have to be entered
  upon changing the checkbox.

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