Flash MX 2004 Games : Art to ActionScript

Chapter 11: Debugging
5 switch(i){
6 case 0:
7 red();
8 break;
9 case 1:
10 green(random(100), random(100));
11 break;
12 case 2:
13 blue(random(9));
14 break;
15 }
16 count++;
17 }
18 trace("Finished");
19
20 function red(){
21 if (_DEBUG) trace(count + ":red");
22 }
23
24 function green(x, y){
25 if (_DEBUG) trace(count + ":green (" + x + "," + y + ")");
26 }
27
28 function blue(i){
29 if (_DEBUG) trace(count + ":blue " + i);
30 if (i>3){
31 if (_DEBUG) trace("Calling red from blue");
32 red();
33 }
34 }
Listing 11.9 ‘Examples/Chapter11/debug14.fla’
Using a debug layer
When your code runs, it will execute so fast that it becomes extremely difficult to work out what is
happening. A debug layer is often useful for more stubborn run-time errors. You create a dynamic
text box on its own layer, which tracks the variable ‘info’, or any other name that you prefer.
Then for each movie clip create a ‘dump’ function. The dump function can be used to add some
information to the ‘info’ variable.
1 //Frame 1 - Main timeline
2 info = Ball.dump();
161