Hi,
which "onstart" do you want to disable?
1. have you defined a onstart on every pano xml (<krpano onstart="...">) and don't want to execute it?
or
2. do you mean the "onstart" parameter of the loadpano() action?
for the 1. type:
when you load a other xml, which has "onstart" attribute, this "onstart" will be
overwritten when you add calls as
4. parameter OR
after the loadpano() call,
e.g. - here a action is called after loadpano():
|
Quellcode
|
1
|
onclick="loadpano(nextpano.xml);action(do_any_thing_instead_of_nextpanos_onstart);"
|
this suppresses the onstart of the nextpano.xml,
or type 2 - when you have already loadpano calls in this format:
|
Quellcode
|
1
2
3
|
<action name="combobox:Front Deck">
loadpano(front.xml,...); wait(blend); lookto(...);"
</action>
|
and want to remove the calls after loadpano(),
there are more possiblities:
e.g. split this into 2 actions, and "change" the "content" of the first
action after the first call:
|
Quellcode
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
|
<action name="combobox:Front Deck">
action(front_deck_load);
action(front_deck_onstart);
</action>
<action name="front_deck_load">
set(action[combobox:Front Deck].content, action(front_deck_load) );
loadpano(front.xml,...); wait(BLEND);
</action>
<action name="front_deck_onstart">
lookto(...);
lookto(...);
</action>
|
in the "front_deck_load" action the "combobox:Front Deck" action
was changed to only "action(front_deck_load)", that means on the next
call of "combobox:Front Deck" only the loading code will be executed,
I hope this was understandable, while witting it down yet,
it sounds a little bit confusing
best regards,
Klaus