Hi nelk,

Zitat

The two variables view.fovmin and vew.maxpixelzoom can be changed dynamically ?

I have tried this:

and it works....

I have tried this:

and it does not work... strange...

Zitat

When both are set, which one is used ?

I have used this code to test:

It seems that, when the 2 attributes are defined inside the <view> node, maxpixelzoom has the priority....
But, if the fovmin attribute is changed dynamically using set(view.fovmin,1) then the fovmin has the priority....

Hope this can help...

Salut.

Hi,

Zitat von »michel«

It seems that, when the 2 attributes are defined inside the <view> node, maxpixelzoom has the priority....
But, if the fovmin attribute is changed dynamically using set(view.fovmin,1) then the fovmin has the priority....

right - when "maxpixelzoom" is set, it has (always) priority
to disable "maxpixelzoom" set it to "0" or to an invalid value ("null" or any "text")

and also right - when dynamically using set(view.fovmin,1) the new fovmin will work, but only for the moment!
when resizing the viewing window (e.g. when resizing the browser window or when switching to fullscreen), then the "maxpixelzoom" setting will work again,

internally it works like this:
when "maxpixelzoom" is set, the "fovmin" will be calculated automatically depending on the window size and the resolution of the panoramic image, and on any change of these both 'parameters' it will update and calculate the "fovmin" value again,

best regards,
Klaus

Zitat von »klaus.krpano«

internally it works like this:
when "maxpixelzoom" is set, the "fovmin" will be calculated automatically depending on the window size and the resolution of the panoramic image...

Is it possible to have the formula to calculate the vertical 'fovmin' from window size ('stageheight'), the resolution of the panoramic image (size of cube faces) and 'maxpixelzoom' values ? thanks...