So are you saying that Inquisit isn't providing me with information about runtime errors here? Isn't that a pretty major design flaw for a coding program? Lol.
Most likely yes. Or you have a script.abort() condition in your script that is triggered.
I don't have a script.abort() condition so that can't be the case.
Apart from reviewing your code accordingly, you should take note of when / where the seemingly random exit occurs and work backwards from there. In all likelihood, the exit isn't random at all, but systematically tied to an issue with your script that occurs under specific conditions.
I can't because the Inquisit application exits and I have to reopen Inquisit 5 every time, so it's impossible or me to see where the problem is occurring. If there is a runtime error, why is the entire Inquisit 5 program exiting? I've never once had this problem with any of the programs I've written in different platforms. Shouldn't the script just terminate and it take me back to the Inquisit window rather than closing the entire program?