[ptx] post 0.5 "mapping" tab

[Philippe Gac]

hi again,
> -----Message d'origine-----
> De : ptx-bounces at email-lists.org [mailto:ptx-bounces at email-lists.org]De
> la part de Rob Park
> Envoyé : 04 June 2005 09:45
> À : Ptx list

> I agree with all of this so far, for a "preview" tab to replace the
> preview window.

I do not agree: both are useful

the big self contained window has its own size and is visible with any other item you wish so you don't have to switch
tabs too often. But it could be merged with the image position window provided some features are implemented
- zoom/scroll/crop
- grid
- outline of pic boundaries
- pic number

there would be an "mapping" tab
- pano projection type recti/cyl/equi/... and their specific parameters if need be
- fov hor/vert with checkboxes "always fit" and buttons "fit"
- crop hor/vert
- quick preview

there would also be an "output" tab
- checkbox "always optimal size" or dropdown list "always optimal size"/"always n% optimal size".../"manually fixed
size"
- image type...
- blending options...
...

There remains
- buttons "center hor/vert"
- checkboxes "always center hor/vert"
perhaps they could be better placed on the "images" tab, with other things that relate to position
BUT one could simply suppress them
- by default, always center hor/vert
- optionally, define one or more "horizon-points" on one or more images that should be at pitch 0 (or opt. 2 parallel
horizontal lines?)
- optionally, define one or more "meridian-points" on one or more images that should be at yaw 0
they would be set up in a CP window
Anyway, it is already done as
- 2 vertical lines determine pitch
- 2 horizontal lines determine yaw
at least in recti projection; should they be optimized separately to work in other cases?

btw, it would be nice to have some restrictions on values
- allowed range -90<pitch<90 (convert to pitch-180 and roll-180)
- allowed range 1 < len_fov < 180 (not hugin dependent, alas)

regards

philippe