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:
|
Quellcode
|
1
|
delayedcall(0.09, nav_animate(%1));
|
do this:
|
Quellcode
|
1
|
if(loaded, delayedcall(0.09, nav_animate(%1)));
|
best regards,
Klaus