[Tweener] try...catch-es

[Makc]

Hi Arthur,

 the idea was to debug code before it goes online, so that onError
handlers could be safely left empty/unassigned. Right now, to do that
I had to comment out try-catch-es completely.

On 5/5/08, Arthur Debert <arthur at stimuli.com.br> wrote:
> Hi Mack.
>
> > catching errors in onupdate/oncomplete makes it difficult to debug
> >  those handlers, since debugger does not stop there and continues code
> >  execution. it _may_ be good idea in release swf (though the idea of
> >  code throwing errors does not sound good in 1st place, plus error
> >  catching is extremely slow), but could you give us some sort of
> >  "pleaseThrowMyErrors" switch so we wouldn't have to go there and
> >  comment it out manually?
> You can add an onError callback that will let you know when something
> goes wrong inside one of your callbacks. The onError is a general
> callback, that will run for exceptions raised on onUpdate, onComplete,
> onStart and so on. There is no way to specify error handlers for each
> callback in particular.
>
> The errors on callbacks had to be caught, or else they would interrupt
> regular flow inside Tweener itself, and that cause a lot of damage.
>
> Notice that if your onError handler also throws an error, Tweener will
> trace it. (no meta onErrorError handler ;-).
>
> Cheers
> Arthur Debert
> >  _______________________________________________
> >  Tweener mailing list
> >  Tweener at lists.caurinauebi.com
> >  http://lists.caurinauebi.com/listinfo.cgi/tweener-caurinauebi.com
> >
> _______________________________________________
> Tweener mailing list
> Tweener at lists.caurinauebi.com
> http://lists.caurinauebi.com/listinfo.cgi/tweener-caurinauebi.com
>