On 6 Feb 2017, at 21:25, Sean P. DeNigris <sean@clipperadams.com> wrote:
How about...
Into
Step into the highlighted message, i.e. dive the debugger into the method which handles it
Over
Step over the highlighted message, i.e. execute it, but keep the debugger focused on the current method
Through
Like stepping "Over", except step through block contents when executed
Restart
Rewind to the start of the current execution context, resetting all local variables
Continue
Relinquish debugger control and proceed with normal execution
Well simpler is of course better, but I think that the aspect of telling what the debugger will do, where it will stop is quite important. Unless it is clear for everybody that step implies to stop and having control return to the debugger.
----- Cheers, Sean -- View this message in context: http://forum.world.st/QA-Debugger-buttons-explained-tp4933212p4933238.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.