Steve (aka Smurf), I am running my debugging session on a ZeroBrane session I started by hand with debug server running. I have also enabled multiple ZB instances so I can continuously edit my module code that supports my custom screen set. As expected, additional ZB instances are started as I need to edit screen element events, etc. I make my changes and exit out, leaving my first debug server session running - just fine.
It's a bit annoying to have to start and close the screen editor in order to debug the ScreenScript at startup. Is it possible to add a button to the Operator list that simply restarts/re-initializes the Mach engine so that the ScreenScript gets ran again without having to start and stop the screen editor? It might be wise to tie it explicitly to the Mach4GUI debug flag (-d) being passed at startup and only show it in debug mode.
I notice I can be in debug mode and running the screen set (aka not in the screen editor) and hit the "Break execution..." button on the debug server and that will drop me in to the debugger at some random point that was executing. But it would be nice to explicitly restart the ScreenScript without the over head of the screen editor.
-Freeman