Hi, Dimster. Good to have you back, and sorry to hear about your loss.
Do you have a recommended or optimal Width and Height which you use?
You'll really have to experiment with it, since our screens will vary. I, for example, have a second screen.
In the latest dev build, there's an option in the Debug menu to have the watch list be output to the console instead - works pretty well with a small list.
Also, it appears there is no "Run To" option which would have your program run to a particular line and then pause.
Or by holding down the mouse button on "Step Into" that you run through the code just to see the changes in the watch list values a little faster than one click at a time.
There's a contextual menu accessible with a right-click that only appears while in $DEBUG mode. You will find "Run To This Line" there.
Regarding a faster way to step into,... well, I'm so used to only doing these debug actions by using the keyboard that I think you should try it too. I even forget we can click the buttons at the bottom, really.
Also, at the end of the program run and the we get the message "Debug session aborted" "Discontinued", is there a way to see the final values of the array in the Watch List?
Since there's no connection to the debuggee anymore when execution ends, I recommend you put a breakpoint at the very last line of your program, so you have time to inspect variable values one last time before execution is done with.
Thank you for trying it!