Catch runtime error / Identify the blocks that cause it

If the Original Post was a complaint about the lack of a stack trace to accompany AI2 error messages, I wholeheartedly agree.

Things not mentioned that would have made debugging easier:

  • block experiencing the error
  • procedure enclosing that block
  • Event enclosing the block or called procedure
  • Screen enclosing that event
4 Likes