Yes, I was really attempting to use the debugging function of Script Debugger. I had set up breakpoints, I was showing the log window, the variables window, the execution stack window and the results window. I had intended to run the script until it hit a break point. I clicked the " run triangle", and all of these windows remained blank. There is a button that indicates running or stopped, it indicated running for about 0.5 seconds, and then indicated “stopped”.
I decided that could still inspect the part of the script that I needed if I deleted about half of the code. So I did that, and the Script Debugger worked as expected. The various windows showed variables, events, execution stack and results, and the code executed to a break point, and afterwards I could step theough the code one line at a time.
With this, I was able to find some logic errors in my script, and refine the code…
It seems to me that there is some part of the initialization of Sript Debugger that encounters an exception and stops, and somehow that condition is not reported nor explained, so the user has no idea what the cause might be.
Perhaps the developers and maintainers of Script Debugger might discover the reason.