You can add conditions to the beginning of the onFirstWindowOpen script to exit early, but otherwise I don't think you can disable them in an ad hoc fashion.
David Moyer wrote:
Is there a way to prevent the File-level script triggers from executing scripts when opening a file?
Turn them off?
If you can't or don't want to do that (you don't mention why you ask this question), then a trap at the front end of the script to exit if conditions warrant it (as Peter mentioned) is the right answer.
It was a hypothetical question.
What if I was confronted with a file that immediately went into an infinite loop.
I've had experience with other software where holding down a hot key would change the startup process.
"With great power, comes great responsibility." - Marvel's Uncle Ben to Spider-man
This applies to the script triggers! I also use hot keys to halt scripts (also testing for access levels). I'm very cautious when setting and using triggers (of any kind) as they do have consequences if not planned well enough.
1 of 1 people found this helpful
Others say if you have FMA, open the script debugger before you open the file.
I remembered that software - it was Mac OS.
There were keys you could acrobatically hold down during startup to make the boot run differently. It's been a long time.
I tested this - having Script Debugger open works, of course.
Thanks to all.