Detailed traces picks up traces where Flash stopped. Adding trace() calls to your code is the first form of debugging a flash project. As you add trace() calls to your code you map out a sort of breadcrumb through your code, getting feedback on what is going on. This works fine with Strings, Booleans, Numbers and ints, but not so well when it comes down to Arrays, XML and Objects. To display these data types you would have to write custom functions that break the data up in elements the trace() function can use. It might be good to know that we have done all this for you and integrated it in a very usefull way into De MonsterDebugger.
If you use De MonsterDebugger in any of your applications you can trace anything you want, simply by calling MonsterDebugger.trace() instead of the standard trace(). No matter what kind of data you are tracing, De MonsterDebugger finds out what it is and displays its content in an understandable way. So whether you want to trace an Object, an Array, an XML with Arrays and Objects or a custom Class, you can trace it using De MonsterDebugger. In addition to this you can assign a color to your trace. For example to distinguish between traces from different team members.
