Debugger Settings
Controls if, in case of an unhandled exception, the debugView
should be opened immediately or instead, a notifier should come
up asking the user.
If turned on, an error notifier will be opened, which shows the top
5 contexts of the calling chain and gives a chance of
proceeding, aborting or debugging.
Developers might prefer the default, which is to go into the debugger
immediately (saves another confirmation-click).
The debugView may show the context backtrace (i.e. the calling chain)
either in a dense mode, where intermediate contexts (such as
"Block>>value"
and some other less
interesting stuff) are hidden, or in verbose mode, where all contexts
are shown.
This toggle controls the default, to be used by a debugView initially.
(Notice, that the debugViews popUpMenu always allows the mode of to be
changed later.)
Most people prefer the dense mode, which shows a less confusing, compact backtrace.
Similar to the above flag, the debugger will hide intermediate contexts,
which implement enumeration or exception handling or similar code.
(in the collection and exception hierarchies).
For example, when a method calls the "select:" method, intermediate contexts in the collection (such as do:) are skipped,
and only the caller and the called block are shown.
Most people (especially beginners) prefer these contexts to be hidden.
Toggles between the new layout (single-step buttons in the middle) and the old layout
(buttons at the top).
Simply enables the debugger's "Report Error" menu items. This function will send a backtrace and
exception information via email to exept, as a bug report.
Copyright © Claus Gittinger Development & Consulting, all rights reserved
Doc $Revision: 1.10 $ $Date: 2000/02/14 14:26:16 $