I use your solution and FP10.1 loaderInfo.uncaughtErrorEvents.addEventListener(UncaughtErrorEvent.UNCAUGHT_ERROR, uncaughtErrorHandler);

But all of them can not catch the Error from a Module.

Do you have some idea about that?

In a typical application, those will be the majority use case. Most of your heavy-lifting logic will be in handlers that are in RPC calls or similar calls that will be in some ways invoked in a callLater-fashion. But I agree-it is not the best solution. If you are on FP10, use the above link.

catchCallLaterExceptions:Boolean [read-write]
A global flag that can is used to catch unhandled exceptions during execution of methods executed via callLater

So, if there’s a error occured not in calllater function, then handleErrors above will not execute.
so, to catch and handle global errors througth catchCallLaterExceptions is not a smart way.

As Jimmy” Gianninas points out, every Flex movie is made up of only two frames, one for initialization and one in which the application executes. The latter is redrawn many times per second — some Flex APIs have immediate effects and others have effects on later refreshes.

callLater() allows you to queue up a method to be called on the next screen refresh. It is often used to wait until some UI work can be done. In this demo, I use it to separate the error from the click handler.

This article from Adobe has more examples:
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7b06.html

Thanks for the tip. With the understanding that “there is no way to catch it on the initiating thread” I’m able to call my error handler using callLater method.

I would highly appreciate if you point me to some resources regarding different use cases of callLater()

Regards

Are you able to run the demo to get the desired effect?

It may be an issue with where the errors are originating from. This post finds that if an error is thrown by an event dispatcher, there is no way to catch it on the initiating thread. That is why, in my demo, I use this click handler:

click="callLater(throwError)"

Instead of:

click="throwError()"

Typically in a large MVC application, this is not an issue, as the handlers are very simple and just dispatch events. Most frameworks (Mate, Cairngorm, etc.) encourage this pattern. However there are certainly times where this is not the case and care has to be taken to ensure that the exception code will be in the callLater queue.

Thanks, I was looking for exactly the same thing.

However, this technique is not working in my project and I have no wild idea why is it so ?

In case of an error, the control never reaches the error handler.

Any ideas ?

Regards