I see, but isn't it just their existence what we want to test for to prevent from loads of Debuggers appearing?
Or should we go the other way around and signal a "DebuggerRaisedNotification" each time before opening a debugger?
However, currently, a #deprecated call in a drawing method makes the image unusable ...
Am 22.10.2019 18:50:59 schrieb Thiede, Christoph <christoph.thiede@student.hpi.uni-potsdam.de>:
Why isn't it sufficient to test for UnhandledError instead? Otherwise, we would also need to test for Warning etc. ...
Von: Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Taeumel, Marcel
Gesendet: Dienstag, 15. Oktober 2019 13:18:26
An: gettimothy via Squeak-dev
Betreff: Re: [squeak-dev] The Trunk: System-mt.1093.mczYeah, I wonder whether we should expand "Error" to "Error, Halt"?
Best,MarcelAm 15.10.2019 12:45:42 schrieb Balázs Kósi <rebmekop@gmail.com>:
Hi Hannes!
This morning I've just run into this exact same situation: putting a halt into a method, called by a morph's #drawOn:makes the image unusable.
The problem stems from WorldState >> displayWorldSafely: being safe only for Errors and not for other kind ofExceptions, and Halt being only an Exception not an Error.
For a quick fix add Halt to the handled exceptions in #displayWorldSafely:[aWorld displayWorld. finished := true] on: Error, Halt do: [:ex |Balázs