Hi,An HTML file (from QTVR example) has the following statement works just fine, but got error message "download of ..... failed" when it has 2 or more deeper levels of subdirectory such
"../../testpano.mov" or
"../../../pano/testpano.mov"
of course the referenced mov file was there. What could be wrong?
Just FYI, I did a quick test and this is fixed as well in the Beta7I just came across something funny with the trace function: when invoked from the 'onload' event handler, it issues the whole event code instead of just the parameter.
E.g.:
![]()
Quellcode
1 onstart="trace(onstart);lookto(100,20,80);"
Will print
![]()
Quellcode
1 trace(onstart);lookto(100,20,80);
in the console...
|
|
Quellcode |
1 |
onclick="tween(view.fov,60,1);tween(view.hlookat,70,1);tween(view.vlookat,0,1,load(cncs_02.xml,null,MERGE,ZOOMBLEND(1,2));" |
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »sagedavid« (8. April 2009, 10:37)
David, see my comment in your other post ...It looks like if krp consider that, after one revolution, 0° is no more 0° but 360°, two revolutions 720°, etc.
hmm, I will think about it,Klaus, don't you think it's possible to include this it the krpano.swf ;-) ?
|
|
Quellcode |
1 2 |
adjusthlookat(50,0); tween(view.hlookat,50); |
Maybe this one more interesting... In this way, the one who want to make two loops still can ;)...I add a function to that adjusts the "hlookat" before doing the tween
e.g.
![]()
Quellcode
1 2 adjusthlookat(50,0); tween(view.hlookat,50);
where 50 would be the destination value, and 0 the number of loops it should make
to reach this value...
Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von »sagedavid« (8. April 2009, 13:57)
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Tim« (11. April 2009, 22:32)
Hi, the selection of the current best multiresolution level has changed in the 1.0.8 version andI seems to me, that multiresthreshold don't work anymore.
the Tab and '9','0' keys are only enabled in this beta version,
they will be disabled in the final version,
maybe I can already disable them in the next beta...