Ferenc Engard
11/29/2003 6:30:00 PM
> > There are a few situations when ruby code runs in a way that the raised
> > exceptions are swallowed by the ruby/tk code (I suppose). I didn't look
> > much after it, but one of this is when ruby code runs as an 'after'
> > callback.
>
> TkAfter had a bug on treatment of TkAfter#cancel_on_exception=(mode).
> I fixed it on CVS.
> If you set TkAfter#cancel_on_exception = false, Tk will show an error
> dialog box when the after callback cause an exception.
> The default value of cancel_on_exception is true.
Why? :)
Why should an uncatched exception be quiet? I think that is a
programming error, more often than not. Although, I mostly use TkAfter
for 'after idle', not for repeating tasks, so it is possible that this
alters my point of view.
Thanks for the bugfix.
Ferenc