We've noticed that if there is a coding error in a message handler, for a
menu say, that it is not shown at all in Boa when in debug mode.
If you are single stepping through code and you have an error e.g. trying
to access an attribute that doesn't exist, the target program just
restarts again - debug finishes.
If you're running outside Boa and the debugger the cmd window associated
with the Python program shows an exception.
One solution is to put try/except around the content of every message
handler, catching StandardError. Using something like ErrorDialog.py from
http://starship.python.net/crew/hochberg/ gives more information to the
Is there something that we're missing? Is there some setting that will
catch and show these exceptions?
Get latest updates about Open Source Projects, Conferences and News.