Hi Allan, 2011/6/19 AKS-Gmail-IMAP <[email protected]>
> Harry, > > I think the following statements are true. > > *Things are fine in Leopard only a long as PTBatcherGui is not already > running.* > > In Leopard, Assistant tab mode launches PTBatcherGui with the correct > project output prefix, either same named or new named and automatically > starts all stitch processes that may be already "waiting" in the > PTBatcherGui queue. The already "waiting" entries would have been in that > state when PTBatcherGui was last closed. > > > In Leopard, the Stitcher tab mode launched PTBatcherGui behaves exactly > as the Assistant tab mode launched PTBatcherGui. > > *Problems occur when PTBatcherGui is already running.* > > **When the PTBatcherGui is empty then nothing is added to the queue > regardless of launching from the Assistant tab or Stitcher tab. > > When the PTBatcherGui is not empty then: > > In Leopard, Assistant tab mode launched PTBatcherGui, the first > PTBatcherGui entry status, *if it is the same project*, changes to > "waiting", but the output prefix remains as it was. Nothing is added or > changed to the queue when none of the existing entries are the same as the > active project. The position within the queue list does not change the > results. In other words the status field changes to "waiting" for the active > project entry regardless of its position in the queue list. This also > happens to any multiple active project named entries. They all change to > "waiting". Automatically starting the stitching process does not occur for > any entries. > > I found different behaviour which I think I will file as bug. I do run the same tests you do off course. What I found is that projects *already finished* were executed again if PTBatcherGui is (still) open. The status completed seems to be reset to waiting when PTBatcherGui is started with a project with the option "-b". > In Leopard, the Stitcher tab launched PTBatcherGui does not exhibit the > above describe behavior. No new entries are added to the queue list or are > any existing entries changed to "waiting". > > *Some things in Tiger are different. Tiger is also not taking any new > prefix names.* > > Behavior in Tiger is similar to what is described above except for some odd > differences. > > The output prefix is always the project name. Whatever different file name > one enters to specify the output prefix is lost. > > No automatic starting of the stitch process occurs in any of the launch > modes. > > The PTBatcherGui list entry status changes to "waiting" happens for all the > same project entries *only for the Assistant tab mode > launched PTBatcherGui*. None of the existing PTBatcherGui same prpject > list entries change to "waiting" when Stitch tab launches PTBatcherGui. The > newly added entry will be "waiting" and its output prefix is will be the > project name as previously mentioned. > > Maybe I didn't mention this clear enough in this first post or previous posts, but Snow Leopards open does not run on Tiger as you tested yourself. So on tiger I simply use the Tiger syntax for Tiger's own open. As that Tiger open is a very simple one I can't give parameters like "automatic start" or panorama name prefix. It will just add the panorama to the queue and that's all. Note though that on Tiger the "old" stitcher application works correctly. So on Tiger you can set in the Preferences the "stitcher engine" (can't recall the exact name right now and I'm hurs from my Mac aways) to Sticher instead of PTBatcherGui. Harry -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
