• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 18. Debugging > Identifying Bugs

Identifying Bugs

As mentioned earlier, there are several ways to restrict the number of bugs that occur in your project. However, we all know that bugs are going to happen anyway. For example, you may have a button that isn't responding to an action, or a handler might be missing some syntax, or your variables might not be changed based on a mislabeled target path. Whatever the problem, tools are available to rescue you—tools such as the Output panel with trace actions and the Error object class. You can also use the Watch, strict type settings in ActionScript, the Bandwidth Profiler, and the Debugger to assist you in identifying bugs in your project.

One problem with discovering bugs is that code blocks are read by Flash in a very short period of time. Within milliseconds, Flash tries to accomplish the tasks set out in a code block. Just watching a movie in the Flash Player will not always allow the human eye to pick up what problems are currently in the project. Furthermore, variables are used in basically all the projects in which you write ActionScript, and you cannot see these variable values simply by watching the movie in the Flash Player.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint