Imagine you’ve made a very huge flash application and many users will play with it every day.
Imagine they don’t have the flashplayer debug installed and at certain points they fall into undiscovered application bugs ( it’s impossible to have a real bug free application, we know this ).
Then, what happens? With the flashplayer debug installed you can see the traceback and you can also continue or dismiss the code execution. But without the debug player? The code will try to continue but probably at that point your application is broken and users will feel it more and more uncomfortable with it.
What I would like to have in flash, and probably you too, is a global system exception handling for those unhandled exception.
In this way you can both present the problem to your users and then also create a report system which will help you to improve and fix your own application!
Something like I did with SEPY years ago using the sys.excepthook of python:
When an exception is raised and uncaught, the interpreter calls sys.excepthook with three arguments, the exception class, exception instance, and a traceback object. In an interactive session this happens just before control is returned to the prompt; in a Python program this happens just before the program exits. The handling of such top-level exceptions can be customized by assigning another three-argument function to sys.excepthook.
Share with...