On Sat 20-Nov-2010 at 14:54 -0700, Jan Martin wrote:
But the result is not as good as what hugin does with the same
.pto, and me just clicking the Stitch now! button on the
Stitcher tab.
You should be able to reproduce exactly the results of using the
1,2,3 buttons from the Hugin Assistant
KFJ!!dude youre the man!!!thanks for informing me about gawk!!i didnt know
it could do that...i was reading a bit about panotools script, but almost
all the tools work on a single pto file..and all th escripts i ahve seen so
far are based on a single pto file..whatever name it has, like
Hi developers
There are plenty of graphics files throughout the codebase. While preparing
to give Hugin a face lift using Cristian Marchi's new design, I've looked at
cleaning things up and documenting them so that when the next designer comes
and want to give Hugin a facelift, things are
Hi Thomas,
thanks for the feedback - and for adding the new naming convention to the
batch stitcher too!
On November 21, 2010 08:20:44 am T. Modes wrote:
The patch needs some more work.
Yes, I knew that, and I was looking for feedback. I have also mixed feelings
about continuing working on
On Nov 21, 5:09 pm, Yuval Levy goo...@levy.ch wrote:
WINDOWS INSTALLERS
...
I'll update his SVG files with the new branding. What I don't understand
(Matthew, maybe you can help?) are the xcf (gimp) files. They contains layers
of what seems to be rendering of the SVG source file, for the
Hi Mac developers,
Mac icons are currently duplicate. There is an Hugin.icns and an
HuginFiles.icns in ./src/hugin/hugin.hg/mac/ and ./src/hugin1/hugin/
which set is actually used? is it possible to use only a single set, ideally
the one in ./src/hugin/hugin.hg/mac/ for both Xcode and CMake
Thanks for the quick reply, Matthew.
On November 21, 2010 10:14:39 pm Matthew Petroff wrote:
the .xcf files could be removed if the icons are generated
directly from the .svg files with scripting.
OK.
For Windows XP the recommend icons are 16x16, 32x32, and 48x48 sizes
in 4-bit, 8-bit,
