WAD Won't Execute Call

[CityguyUSA]

This is crazy. I'm spending more time debugging your debugger than I am my scripts.

This highlights the call as the current line but will not execute.

 

[rconn]

This is crazy. I'm spending more time debugging your debugger than I am my scripts.

This highlights the call as the current line but will not execute.
View attachment 5875

CALL works fine here. Are you singlestepping or just running to the breakpoint?

If you're singlestepping, you have to "step into" to go to the CALL'd batch file. A "step over" will execute it but not put the debugger into the call'd file.

 

[CityguyUSA]

This isn't the first time I ran the script. It was working fine as far as actually loading and accessing the script via the debugger. Now I have to load the sub-script as the main script to get it to run. This calling script is the one that's jumping if statements and saying the current line is way out of where it should be. Hard to know if it's part of that problem or something else. I ran up to the breakpoint prior to the call then single-stepped so it would walk into the new script but it didn't load it just went to the line after the call multiple times.

 

[rconn]

Did you "step into" the CALL'd file? (Which will open a new tab window with the second batch file.) Or "step over"? (Which will execute the second file but not display it, and then move the execution pointer to the following line.)

 

[CityguyUSA]

Attempted to step-into but it didn't do that.