Hi,
regarding to the discussion here in the PanoToolsNG List about the field of view (FOV):
http://tech.groups.yahoo.com/group/PanoToolsNG/message/33817
I thought it would be a good idea to make the type/base of the FOV adjustable in krpano,
at the moment the FOV value (view.fov) in krpano defines the vertical FOV,
now I added a new setting - view.fovtype (xml: <view fovtype="VFOV" />)
it defines the type of the fov value,
it can be:
- VFOV - vertical field of view (the default)
- HFOV - horizontal field of view
- DFOV - diagonal field of view
- MFOV - 'maximum' field of view (a mix of VFOV and HFOV, works like the FPP fov)
here an online demo with adjustable fovtype and various window sizes:
https://krpano.com/examples/fovtype/
here a new 1.0.8 beta 9 pre-release package for downloading:
krpano-1.0.8-beta9-build-2009-10-29.zip
and here a some explanation images about the fovtype:
VFOV
- based on the vertical window size
- the VFOV is fixed and the HFOV will change on window resize
HFOV
- based on the horizontal window size
- the HFOV is fixed and the VFOV will change on window resize
DFOV
- based on the diagonal window size
- the DFOV is fixed and the HFOV and VFOV will change on window resize
MFOV
- based either on the horizontal windowsize or on the, by 4/3, scaled vertical windowsize
- the MFOV is fixed and either HFOV or VFOV will change on window resize
the demo above also includes an adjustable "maxpixelzoom" setting,
the "maxpixelzoom" setting set how much the original pano image can be scaled/zoomed, based on the panoramic image resolution (maxpixelzoom=1.0 => 100% pixel view),
but note - at larger field of views the scaling of the original pano image is not constant over the entire screen (it is distorted - more scaling/distortion at the 'edges', fewer in the 'middle'), the "maxpixelzoom" respects that and when the resolution of the pano is too low, it limits the zooming already before reaching a real 1:1 pixelview in the middle area,
best regards,
Klaus