On Sat 02-May-2009 at 15:21 +0200, J. Schneider wrote:
>
>- I have a few questions and suggestions concerning the GUI. After some
>feedback I might file feature requests or bug reports.

Yes these are definitely worth putting in the tracker.

>First of all a question for me to understand: As far as I understood in
>an other thread, PTBatcher and PTBatcherGUI are both standalone
>programs, so PTBatcherGUI is not simply a GUI for PTBatcher? If so it is
>irritating, but never mind.

It's the other way around, PTBatcher is a command-line version of 
PTBatcherGUI.

>7.
>There is an option to always overwrite existing files. Could you add an
>option to reuse them? When my unstable machine crashes in the middle of
>an hour of blending it would be nice to have the possibility to skip at
>least remapping.

In principle this is possible, the Makefile stitching system can be 
stopped and will restart at the same point (you get this if you 
stitch on the command-line with 'make -f').

I'm not sure how it works with PTBatcherGUI, all the intermediate 
files are created in a temporary location with a randomised name, 
but probably this name is different when you restart, so the 
previously generated intermediate files are unavailable.

>Just while I'm writing one project fails because I used the # character 
>in the file name.
>"d:\tmp\hug3B6.tmp:552: warning: overriding commands for target '#'
>... no target ..."

Most of these 'special character' bugs were fixed since 0.7.0, it 
looks like you found a new one.

-- 
Bruno

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to