Debugging JSL Code with the JMP Debugger is nothing I can recommend. As we strive for more and more automated analysis within our customer base to widen the use of JMP, debugging is a key!
Current situation:
* Debugger starts a new instance and is distinct from the code in the original editor
* the functionality is good for getting running times to identify lacks, but not for actual debugging
* Finding something and immediately change and test again is not possible, you have to close the debugger, find the line of code, change it (hoping you got the message right), opening the debugger again, run the code and start again the loop.
* That results most people do not open the debugger but select serially code in the editor and run it, changing indices of loops manually to simulate a for loop.
Preferred solution:
* new instance is fine as most other tools are doing this as well (but only for the calculation!)
* Good tools have the debugging embedded in the editor, so you can set breakpoints and checkmarks directly in the editor.
* Changing is possible without to stop debug modus and all you run is in a "virtual debug scenario".
I know we do scripting, however everyone would benefit from this. Programmer are familiar to (and expect) this behaviour, people new to JSL can eliminate issues way faster.
