On Feb 6, 2011, at 9:51 AM, Harry van der Wolf wrote:
No idea how I got that copy&paste action incorrect. See correct link
below.
<http://hugin.panotools.org/testing/hugin/Hugin-nopatch.app.zip>
The same for me:
echo: write: Bad file descriptor
gnumake: *** [info] Error 1
At least this time the progress window stayed open and revealed some
possibly useful information. When using 2010.5.0.4886:a1cb4a2efa65,
that window flashes briefly and disappears.
Earlier, I tried using PTBatcherGUI.app and although it is hardly a
good replacement for Hugin working correctly I *was* happy to see a
quite verbose log printed to a window.
I wish there were a way for Hugin itself to (optionally) produce such
a thing. If Hugin doesn't "leave notes" somewhere about what is
happening, how will we ever be able to track down some of the more
obscure misbehaviors?
Thanks,
eo
--
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