Tools become unresponsive when debugger open on some errors
In the GUI framework introduced in the VisualWorks 8.x environment, editor panes may become unresponsive when a debugger is open on certain kinds of errors that arise from evaluating code in that editor, using the pop-up menu.
For example, a do it or GS-do it that gets a message non understood error will require that the debugger be closed on that error, before you can edit text in that editor.
Workaround
Using the toolbar or edit menu options to execute code avoids this issue, and closing the debugger allows normal operation to continue.
Last updated: 7/15/16