hotspot scale animation

Razek · July 14, 2011 at 12:25 PM

I have scale animation hotspot with this style:

Code

<style name="nav_hotspot_anim"
  url="skin/arrow.png" 
  alpha="0.3"
  distorted="true"
  scale="1"
  scalemax = "1.2"
  animation = "true"
  incr = "true"
  keep="false"     
  onloaded="nav_animate(get(name)));"
  onover="tween(alpha,1);tween(scale,1.3); set(animation, false); toggle_autorotate(false);"
  onout="tween(alpha,0.6); set(animation, true); toggle_autorotate(true); nav_animate(get(name));" 
  />

Display More

I have some hotspots with the Identical names
in different scenes, when i move from scene to the scene and back with Identical hotspot names, the speed of animation was doubled. How i can to resolve this problem without to rename hotspots?

klaus.krpano · July 14, 2011 at 5:58 PM

Hi,

please show also the code of your "nav_animate" action,
the problem may be located there,

when the speed was doubled it could be that now something will be called two-times,

best regards,
Klaus

Razek · July 15, 2011 at 9:36 AM

Code

<action name="nav_animate">
  trace('ACTION: nav_animate[',get(name),'] scale=', get(hotspot[get(name)].scale),' animation=',hotspot[%1].animation); 
  ifnot(hotspot[%1].scale === null,
  if(hotspot[%1].animation === true, _nav_animate(%1));
  );
        </action>
 <action name="_nav_animate">
  if(hotspot[%1].incr === true,
   if(hotspot[%1].scale GT hotspot[%1].scalemax , set(hotspot[%1].incr, 'false'));
          inc(hotspot[%1].scale,0.02)
  );
  if(hotspot[%1].incr === false,
   if(hotspot[%1].scale LT 1, set(hotspot[%1].incr, 'true'));
          dec(hotspot[%1].scale,0.02)
  );
  delayedcall(0.09, nav_animate(%1));
       </action>

Display More

klaus.krpano · July 23, 2011 at 12:02 PM

Hi,

okay, there is no stop condition for the case when the hotspot was removed,
so the actions will be called again and again, even when the original hotspot was already removed,
and when there is now revisit of that pano with the same hotspots and action, they will be called twice and more,

but there is a easy solution, the attributes of the source/first calling hotspot can be always accesses directly, so it would be possible to check a variable from there (e.g. the loaded variable) before doing the delayedcall,

e.g.
instead of:

Code

delayedcall(0.09, nav_animate(%1));

do this:

Code

if(loaded, delayedcall(0.09, nav_animate(%1)));

best regards,
Klaus

Participate now!