hugin-devs team mailing list archive

[aseidel <830655@xxxxxxxxxxxxxxxxxx>]

On a PPC 4, OSX 10.5.8 , checking Harry's RC5, it appears to be fixed  
although there is now perhaps an unrelated glitch.  I see the  
following benign error message pops up when PTBatcherGUI is not  
already running. "External program linefind not found in the bundle,  
reverting to system path."

Allan


On Sep 26, 2011, at 11:40 AM, tmodes wrote:

> No comment?
> Assuming it is fixed.
>
> ** Changed in: hugin
>       Status: In Progress => Fix Committed
>
> -- 
> You received this bug notification because you are subscribed to the  
> bug
> report.
> https://bugs.launchpad.net/bugs/830655
>
> Title:
>  OS X Hugin reassigns Completed PTBatcherGUI queue list processes
>
> Status in Hugin - Panorama Tools GUI:
>  Fix Committed
>
> Bug description:
>  This bug occurs in OS X Hugin. Hugin reassigns completed stitch
>  processes listed in the PTBatcherGUI queue list to the active project
>  stitch settings for those completed processes that match the active
>  Project name and when any of the Hugin Stitcher controls have  
> received
>  a changing user input subsequent to executing the previous stitch
>  process. Some examples are changing the state (even then restoring to
>  the previous state) for Projection, Size or Output format settings
>  (including Quality) or checking and unchecking a Panorama Output  
> check
>  control.  The status for all these reassigned  processes changes to
>  Waiting and PTBatcherGUI reprocesses them according to the changed
>  settings in a normal fashion prompting to overwrite any existing
>  outputs. The bug changes the PTBatcherGUI queue list moments before
>  the “Specify output prefix” dialog box appears. The workaround it to
>  clear the PTBatcherGUI queue after a stitch is complete.
>
>  To easily observe this bug use a small file image, two image project.
>  Call it project A. Make a stitch named QQQ. Without clearing any of
>  the PTBatcherGUI list make another identical stitch named WWW.
>  Position the PTBatcherGUI window so that Status column will be  
> visible
>  at all times. Change any Hugin Stitcher setting. Start another  
> stitch.
>  Observe the change to the PTBatcherGUI list Status column prior to
>  naming this last stitch EEE. Save the Hugin Project A and save-as it
>  to be Project B. Perform similar tests as for Project A but use
>  different output names. You should see only the Project B list  
> entries
>  being reassigned. Close out Project B and reload Project A. Again
>  perform similar tests. This time you should see only the Project A
>  list entries being reassigned.
>
>  This behavior was observed in OS X 10.6.8 Intel and OS X 10.5.8 PPC  
> or
>  Hugin-2011.2.0_rc3.  Similar behavior was observed on a Tiger Intel
>  system when testing prior versions of Hugin that first introduced the
>  send to PTBatcherGUI method of performing all batch processes.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hugin/+bug/830655/+subscriptions

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

Title:
  OS X Hugin reassigns Completed PTBatcherGUI queue list processes

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  This bug occurs in OS X Hugin. Hugin reassigns completed stitch
  processes listed in the PTBatcherGUI queue list to the active project
  stitch settings for those completed processes that match the active
  Project name and when any of the Hugin Stitcher controls have received
  a changing user input subsequent to executing the previous stitch
  process. Some examples are changing the state (even then restoring to
  the previous state) for Projection, Size or Output format settings
  (including Quality) or checking and unchecking a Panorama Output check
  control.  The status for all these reassigned  processes changes to
  Waiting and PTBatcherGUI reprocesses them according to the changed
  settings in a normal fashion prompting to overwrite any existing
  outputs. The bug changes the PTBatcherGUI queue list moments before
  the “Specify output prefix” dialog box appears. The workaround it to
  clear the PTBatcherGUI queue after a stitch is complete.

  To easily observe this bug use a small file image, two image project.
  Call it project A. Make a stitch named QQQ. Without clearing any of
  the PTBatcherGUI list make another identical stitch named WWW.
  Position the PTBatcherGUI window so that Status column will be visible
  at all times. Change any Hugin Stitcher setting. Start another stitch.
  Observe the change to the PTBatcherGUI list Status column prior to
  naming this last stitch EEE. Save the Hugin Project A and save-as it
  to be Project B. Perform similar tests as for Project A but use
  different output names. You should see only the Project B list entries
  being reassigned. Close out Project B and reload Project A. Again
  perform similar tests. This time you should see only the Project A
  list entries being reassigned.

  This behavior was observed in OS X 10.6.8 Intel and OS X 10.5.8 PPC or
  Hugin-2011.2.0_rc3.  Similar behavior was observed on a Tiger Intel
  system when testing prior versions of Hugin that first introduced the
  send to PTBatcherGUI method of performing all batch processes.

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