thanks for you post.
Since it is bit of programming innvoled to make Script triggers for a Tab Control.
would it be better off designing different layout that looks like tabs. (create x Noi of duplicates of your current layout )Then you can control each layout with script triggers on the designed Tab.
you can add a Pause/Resume button. with a nice red button for stop and a nice green for start. :)
hope that helps
Thanks for the reply. Really hoping I had just missed something on the script trigger (maybe differences between types). Also like the smooth transition using the built in tab control. Guess I will just stick with the pause/resume button they are currently using before trying to change the layouts.
Just thought of a possible simple solution. How about setting up a global variable as a switch. On the script with the loop that transitions between tabs, before the go to object turn the swith off and then back on before the pause timer. Then on the script trigger with the longer delay for data entry, test to see if the switch is on or off before continuing. That way, the script trigger would ignore when the tab is selected via the loop script.
How about setting up a global variable as a switch.
That would be my approach, too. This will NOT prevent the triggered script from running, though. The trick is to make the triggered script look at the variable and act accordingly. For example, you could make your looping script select tabs this way:
SetVariable [ $$autoSwitch ; 1 ]
Go to Object [ <next tab> ]
SetVariable [ $$autoSwitch ; "" ]
then place the entire triggered script inside an If block:
If [ not $$autoSwitch ]
# actual script steps here
This way, the triggered script will exit immediately - unless it was triggered by user switching a tab while the looping script is paused.
Worked great! Thanks for everyone's input!