<div>Thanks again for the pointer to ToolSet. I use my own new subclass tool set to override common errors like ZeroDivide. <br><br></div><div>However, just returning w/o handling an error like #doesNotUnderstand: seems to leave the process in a loop trying to handle the unhandled error, freezing the UI (until interrupted). </div>
<div><br></div><div><br></div><div>For now, I've changed Object>>doesNotUnderstand: to test if my toolset is the default and just return, but this has the effect of a continue rather than an abandon. </div><div>
<br></div><div>Cheers,<br>Darius</div>________<div><br><div class="gmail_quote">On Mon, Dec 20, 2010 at 11:57 PM, Darius Clarke <span dir="ltr"><<a href="mailto:socinian@gmail.com">socinian@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Thank you.<div>I'll try subclassing the standard one.</div><div>Seems like some errors keep looping if they somehow remain unhandled... like 'does not understand'. DivideByZero doesn't have the problem. </div>
<div><br></div><div>However, I have enough info to proceed for now. </div><div>Thank you again. </div><div><br></div><font color="#888888"><div>- Darius</div>
</font></blockquote></div><br></div>