25 May
2011
25 May
'11
7:42 p.m.
On 25 May 2011, at 12:25, Alexandre Bergel wrote:
the original problem was that I did not get anything. Because the error apparently was trapped.
Yes. Errors are trapped during an interaction. This is the only relatively reliable solution I have found to not get a recursive debugger opening loop.
I understand the problem, have been bitten by it sufficiently when working on AM. But is there a way to display some side-effect so that the developer knows that 'something' has gone wrong? A non-modal dialog box giving some info?
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile