I've been testing the code structure kindly provided by Klaus to setup an
auto tour with user interruption and resume.
In the initial very basic work, I've found I have to use
Tween so I can control the speed or timing of movement around the view.(OK, now see the moveto and others have speed control.) But I've also found that I have to use
Wait before an step increment and set the timing or the next conditional is executed before the action of the first step is finished.
So I'm guessing that each action is fully loaded and acted upon in a object fashion as opposed to a linear process. Is this correct or what else am I missing as I continue to add complexity into the
auto tour.
Here's a small sample of what I've done, without the wait at the end of the first set of tweens - before the step increment - the last tween set, after the wait(17), is executed in the second pano, not the first one as intended.
<action name="
autotour">
oninterrupt(break);
if(step == 1, tween(view.fov,90,20,linear);tween(view.hlookat,370,20,linear);tween(view.vlookat,0,20,linear);wait(17); tween(view.fov,30,5,easeInOutSine); tween(view.hlookat,82,5,easeInOutSine);
wait(8); inc(step); );
if(step == 2, loadpano(DiningRoom_MG_8170 Panorama.xml,null,KEEPBASE|NOPREVIEW,BLEND(2)); wait(2); inc(step); );
...
Just trying to understand this tool, one small tween at a time
Regards,
Robert