Use monster debugger again-a powerful tool for flash debugging

Monster debugger was occasionally used more than a year ago. At that time, I only thought it was a novelty. However, once I used it, I found that it was more troublesome to debug than a common trace, and the output does not change much.
Today, due to the need for the project, I found a third-party debugging tool again, and I was lucky to find it again.
From the original version 1.0 to the current version 3.0, I have tried it and found that it is not the same as today. It is so powerful that it cannot be used.

Such a good thing is a storm of things.

The most obvious benefit of monster debugger is the convenience of debugging.

If you want to debug on the web page, you have to do a few things.
1. Whether you use Flash CS, FD, and flex, you must output the debug version.
2. Use the debug function of firebug
3. Use the debug version of Flash Player
4. Risks of Firefox crash may occur from time to time

Advantages of using monster Debugger:
1. for debugging, you only need to call monsterdebugger. Trace (...);
2. Easily view all objects, frames, and memory usage of the application
---- It is easier to view the performance. For example, check whether some objects are deleted after some operations.

3. From tool to screen: Modify parameters such as alpha, x, y, and scalex in the tool, and the results are directly reflected on the screen.
---- Adjust the UI and you don't need to compile it again.

4. From the screen to the tool: Click [highlight & inspect] of the tool and click the screen. The tool immediately displays the properties of the clicked object.
---- After getting the object easily, modify it directly. What you see is what you get.

5. function: displays objects with visible = false and alpha = 0 on the stage.
---- This function is also good, so that you can compare the hatchback without record the hidden objects in your mind.

6. Do you want to debug the public methods of an object? Click highlight first, select the object on the screen, view the method on the tool, double-click, enter or not enter the parameter, and click Run. See the results now.
----- It feels a little similar to unit test.

7. Easily trace data such as array, object, and XML. You do not need to use the for loop to trace the data.
---- It's really tiring to look up the data in the XML object before, but now it's clear.

8. the breakpoint function in the real environment. FD or FB also have breakpoints. However, if SWF is placed in a webpage environment, breakpoints are not so easy to use. In this tool, you can easily control breakpoints.

---- To be honest, the breakpoint has never been actually used. Do you know if you can add it? :)

Reprinted, please write the source, thank you :)