[ptx] Some suggestions for hugin

[Pablo d'Angelo]

On Sun, 08 Feb 2004, Ed Halley wrote:

I have made some bugfixes....

> > These are not really bugs, just minor wish-list items, things that I
> > notice every time I use hugin.  In no particular order:
> > -  It's very difficult to remember the usage of different toolbar
> >    buttons, it would be much clearer with icons+text style toolbars
> >    instead of just icons.
> >    I figured-out how to do this with xrc, I'll attach a patch.
> 
> I don't know if wx will follow the user's global preference for this,
> but I hope that can be made switchable.

Well, I just added it right now. is probably useful for newbies. One could
always load a different xrc file, if not texts are wanted. 

> > -  I know there is a plan to redo all the buttons, but the only one
> >    that is _really_ wrong is the 'update' icon in the 'Preview'
> >    window which is a picture of a floppy disk.
> 
> Yes, my mistake, I put in the wrong name for the icon.  I had left it
> "momentarily," and here it is a couple months later.

Which icon did you want to use?

> > -  Portrait orientated images get squashed and scaled very strangely
> >    in the tiny previews on the 'Images' & 'Camera and Lens' tabs.
> 
> An all-portrait one-row panorama also can't estimate the vfov properly. 
> Which is a shame, because it's a popular way to make architectural
> quickies.

fixed.

I also fixed the crash at the exit. It was due to incorrect usage of
wxWindows in PanoDruid. wxWindows always wants to destroy its controls with
delete, so they always have to be created with new.

Now, the window size of the CtrlPoint window is saved properly.

I also made it possible to switch the PanoDruid off (to have a bigger
preview). currently only by editing the config file (showDruid=0).

Maybe the druid should be moved to a separate window.

> > -  If there was a 'Stitch with nona' button on the 'Stitcher' tab,
> >    then we could distribute a package with 100% open source
> >    dependencies.
> 
> Amen.  I think nona needs to spit out progress information to feed the
> progress bar, but that should be all that's required (that I know of) to
> make it an alternative tool.

Yes, probably. Hmm actually I'm thinking about writing a gui version of
nona, because all the other frontends need a gui version. (the windows pano
tools pop up their own windows). Or should we just provide GUI support for
nona within hugin?

Bruno, does your PTOptimiser save the optimized points, if it is interrupted
with Ctrl-C?

ciao
  Pablo
-- 
http://wurm.wohnheim.uni-ulm.de/~redman/
Please use PGP