Archive for August, 2007

Listing a SWF file s variables In test mode, (Free web hosting services)

Friday, August 31st, 2007

Listing a SWF file s variables In test mode, the List Variables command displays a list of all the variables currently in the SWF file. This is especially useful for finding the correct variable target path and variable name. Unlike the Debugger, the list does not update automatically as the SWF file plays; you must select the List Variables command each time you want to send the information to the Output panel. The List Variables command also displays global variables declared with the _global identifier. The global variables are displayed at the top of the List Variables output in a Global Variables section, and each variable is prefixed with _global. In addition, the List Variables command displays getter/setter properties properties that are created with the Object.addProperty() method and invoke get or set methods. A getter/ setter property is displayed alongside any other properties in the object it belongs to. To make these properties easily distinguishable from ordinary variables, the value of a getter/setter property is prefixed with the string [getter/setter]. The value displayed for a getter/setter property is determined by evaluating the get function of the property. To display a list of variables in a SWF file: 1 If your SWF file is not running in test mode, select Control > Test Movie. 2 Select Debug > List Variables. A list of all the variables currently in the SWF file is displayed in the Output panel, as shown in this example: Global Variables: Variable _global.MyGlobalArray = [object #1] [ 0:1, 1:2, 2:3 ] Level #0: Variable _level0.$version = “WIN 6,0,0,101″ Variable _level0.RegularVariable = “Gary” Variable _level0.AnObject = [object #1] { MyProperty: [getter/setter] 3.14159 } Displaying text field properties for debugging To get debugging information about TextField objects, you can use the Debug > List Variables command in test movie mode. The Output panel uses the following conventions in displaying TextField objects: If a property is not found on the object, it is not displayed. No more than four properties are displayed on a line. A property with a string value is displayed on a separate line. If there are any other properties defined for the object after the built-in properties are processed, they are added to the display using the rules in the second and third points above. Color properties are displayed as hexadecimal numbers (0×00FF00). The properties are displayed in the following order: variable, text, htmlText, html, textWidth, textHeight, maxChars, borderColor, backgroundColor, textColor, border, background, wordWrap, password, multiline, selectable, scroll, hscroll, maxscroll, maxhscroll, bottomScroll, type, embedFonts, restrict, length, tabIndex, autoSize. Chapter 3: Writing and Debugging Scripts
We recommend cheap and reliable webhost to host and run your web applications: Coldfusion Web Hosting services.

Using the (Web site directory) Output panel In test mode, the

Friday, August 31st, 2007

Using the Output panel In test mode, the Output panel displays information to help you troubleshoot your SWF file. Some information, such as syntax errors, is displayed automatically. You can display other information by using the List Objects and List Variables commands. (See Listing a SWF file s objects on page 77 and Listing a SWF file s variables on page 78.) If you use the trace statement in your scripts, you can send specific information to the Output panel as the SWF file runs. This could include notes about the SWF file s status or the value of an expression. (See Using the trace statement on page 79.) To display the Output panel, select Window > Development Panels > Output or press F2. Note: If there are syntax errors in a script, the Output panel appears automatically when you check syntax or test your SWF file. To work with the contents of the Output panel, use the Options pop-up menu in the upper right corner. Listing a SWF file s objects In test mode, the List Objects command displays the level, frame, object type (shape, movie clip, or button), target paths, and instance names of movie clips, buttons, and text fields in a hierarchical list. This is especially useful for finding the correct target path and instance name. Unlike the Debugger, the list does not update automatically as the SWF file plays; you must select the List Objects command each time you want to send the information to the Output panel. The List Objects command does not list all ActionScript data objects. In this context, an object is considered to be a shape or symbol on the Stage. To display a list of objects in a movie: 1 If your movie is not running in test mode, select Control > Test Movie. 2 Select Debug > List Objects. A list of all the objects currently on the Stage is displayed in the Output panel, as shown in this example: Level #0: Frame=1 Label=”Scene_1″ Button: Target=”_level0.myButton” Shape: Movie Clip: Frame=1 Target=”_level0.myMovieClip” Shape: Edit Text: Target=”_level0.myTextField” Text=”This is sample text.” Using the Output panel 77
If you are searching for cheap webhost for your web application, please visit MySQL5 Web Hosting services.

As you (Web hosting control panel) step through lines of code, the

Thursday, August 30th, 2007

As you step through lines of code, the values of variables and properties change in the Watch list and in the Variables, Locals, and Properties tabs. A yellow arrow along the left side of the Debugger s code view indicates the line at which the Debugger stopped. Use the following buttons along the top of the code view: Continue Stop Debugging Toggle Breakpoint Remove All Breakpoints Step In Step Out Step Over Step In advances the Debugger (indicated by the yellow arrow) into a function. Step In works only for user-defined functions. In the following example, if you place a breakpoint at line 7 and click Step In, the Debugger advances to line 2, and a subsequent click of Step In will advance you to line 3. Clicking Step In for lines that do not have user-defined functions in them advances the Debugger over a line of code. For example, if you stop at line 2 and select Step In, the Debugger advances to line 3, as shown in the following example: 1 function myFunction() { 2 x = 0; 3 y = 0; 4 } 5 6 mover = 1; 7 myFunction(); 8 mover = 0; Step Out advances the Debugger out of a function. This button works only if you are currently stopped in a user-defined function; it moves the yellow arrow to the line after the one where that function was called. In the example above, if you place a breakpoint at line 3 and click Step Out, the Debugger moves to line 8. Clicking Step Out at a line that is not within a user-defined function is the same as clicking Continue. For example, if you stop at line 6 and click Step Out, the player continues executing the script until it encounters a breakpoint. Step Over advances the Debugger over a line of code. This button moves the yellow arrow to the next line in the script and ignores any user-defined functions. In the example above, if you are stopped at line 7 and click Step Over, you go directly to line 8, and myFunction() is ignored. Continue leaves the line at which the player is stopped and continues playing until a breakpoint is reached. Stop Debugging makes the Debugger inactive but continues to play the SWF file in Flash Player. Chapter 3: Writing and Debugging Scripts
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.

You can set breakpoints in the Actions panel (Web server certificate)

Thursday, August 30th, 2007

You can set breakpoints in the Actions panel or in the Debugger. (To set breakpoints in external scripts, you must use the Debugger.) Breakpoints set in the Actions panel are saved with the Flash document (FLA file). Breakpoints set in the Debugger are not saved in the FLA file and are valid only for the current debugging session. To set or remove a breakpoint in the Actions panel, do one of the following: Click in the left margin. A red dot indicates a breakpoint. Click the Debug options button above the Script pane. Right-click (Windows) or Control-click (Macintosh) to display the context menu, and select Breakpoint, Remove Breakpoint, or Remove All Breakpoints. Press Control+Shift+B (Windows) or Command+Shift+B (Macintosh). Note: In previous versions of Flash, clicking in the left margin of the Script pane selected the line of code; now it adds or removes a breakpoint. To select a line of code, use Control-click (Windows) or Command-click (Macintosh). To set and remove breakpoints in the Debugger, do one of the following: Click in the left margin. A red dot indicates a breakpoint. Click the Toggle Breakpoint or Remove All Breakpoints button above the code view. Right-click (Windows) or Control-click (Macintosh) to display the context menu, and select Breakpoint, Remove Breakpoint, or Remove All Breakpoints. Press Control+Shift+B (Windows) or Command+Shift+B (Macintosh). Once Flash Player is stopped at a breakpoint, you can step into, step over, or step out of that line of code. If you set a breakpoint in a comment or on an empty line in the Actions panel, the breakpoint is ignored. Stepping through lines of code When you start a debugging session, Flash Player is paused. If you set breakpoints in the Actions panel, you can simply click the Continue button to play the SWF file until it reaches a breakpoint. For example, in the following code, suppose a breakpoint is set inside a button on the line myFunction(): on(press){ myFunction(); } When you click the button, the breakpoint is reached and Flash Player pauses. You can now step in to bring the Debugger to the first line of myFunction() wherever it is defined in the document. You can also step through or out of the function. If you didn t set breakpoints in the Actions panel, you can use the jump menu in the Debugger to select any script in the movie. Once you ve selected a script, you can add breakpoints to it. After adding breakpoints, you must click the Continue button to start the movie. The Debugger stops when it reaches the breakpoint. Debugging your scripts 75
From our experience, we are can tell you that you can find a reliable and cheap webhost service at Java Web Hosting services.

Displaying movie clip properties and changing editable properties (Adult web hosting)

Wednesday, August 29th, 2007

Displaying movie clip properties and changing editable properties The Debugger s Properties tab displays all the property values of any movie clip on the Stage. You can change a value and see its effect in the SWF file while it runs. Some movie clip properties are read-only and cannot be changed. To display a movie clip s properties in the Debugger: 1 Select a movie clip from the display list. 2 Click the Properties tab in the Debugger. To modify a property value: Double-click the value, and enter a new value. The value cannot be an expression. For example, you can enter 50 or “clearwater”, but you cannot enter x + 50. The value can be a string (any value surrounded by quotation marks), a number, or a Boolean value (true or false). You can t enter object or array values (for example, {id: “rogue”} or [1, 2, 3]) in the Debugger. For more information, see String operators on page 46 and Using operators to manipulate values in expressions on page 45. Note: To write the value of an expression to the Output panel in test mode, use the trace statement. See Using the trace statement on page 79. Setting and removing breakpoints A breakpoint lets you stop a SWF file running in Flash Player at a specific line of ActionScript. You can use breakpoints to test possible trouble spots in your code. For example, if you ve written a set of if..else if statements and can t determine which one is executing, you can add a breakpoint before the statements and step through them one by one in the Debugger. Chapter 3: Writing and Debugging Scripts
If you are searching for cheap webhost for your web application, please visit MySQL5 Web Hosting services.

Using the Watch list To monitor a set (Make web site)

Wednesday, August 29th, 2007

Using the Watch list To monitor a set of critical variables in a manageable way, you can mark variables to appear in the Watch list. The Watch list displays the absolute path to the variable and the value. You can also enter a new variable value in the Watch list the same way as in the Variables tab. If you add a local variable to the Watch list, its value appears only when Flash Player is stopped at a line of ActionScript where that variable is in scope. All other variables appear while the SWF file is playing. If the Debugger can t find the value of the variable, the value is listed as Undefined. The Watch list can display only variables, not properties or functions. Variables marked for the Watch list and variables in the Watch list To add variables to the Watch list, do one of the following: On the Variables or Locals tab, right-click (Windows) or Control-click (Macintosh) a selected variable and then select Watch from the context menu. A blue dot appears next to the variable. On the Watch tab, right-click (Windows) or Control-click (Macintosh) and select Add from the context menu. Enter the target path to the variable name and the value in the fields. To remove variables from the Watch list: On the Watch tab, right-click (Windows) or Control-click (Macintosh) and select Remove from the context menu. Debugging your scripts 73
We recommend you use shared web hosting services, because many users agree that it is cheap, reliable and customer-satisfying webhost.

Displaying and modifying variables The Variables tab in (Web server logs)

Wednesday, August 29th, 2007

Displaying and modifying variables The Variables tab in the Debugger displays the names and values of any global and Timeline variables in the SWF file. If you change the value of a variable on the Variables tab, you can see the change reflected in the SWF file while it runs. For example, to test collision detection in a game, you can enter the variable value to position a ball in the correct location next to a wall. The Locals tab in the Debugger displays the names and values of any local variables that are available wherever the SWF file has stopped at a breakpoint or anywhere else within a user- defined function. To display a variable: 1 Select the movie clip containing the variable from the display list. To display global variables, select the _global clip in the display list. 2 Click the Variables tab. The display list updates automatically as the SWF file plays. If a movie clip is removed from the SWF file at a specific frame, that movie clip, along with its variable and variable name, is also removed from the display list in the Debugger. However, if you mark a variable for the Watch list (see Using the Watch list on page 73), that variable is not removed. To modify a variable value: Double-click the value, and enter a new value. The value cannot be an expression. For example, you can use “Hello”, 3523, or “http:// www.macromedia.com”, and you cannot use x + 2 or eval(”name:” +i). The value can be a string (any value surrounded by quotation marks), a number, or a Boolean value (true or false). Note: To write the value of an expression to the Output panel in test mode, use the trace statement. See Using the trace statement on page 79. Chapter 3: Writing and Debugging Scripts
From our experience, we can recommend PHP5 Web Hosting services, if you need affordable webhost to host and run your web application.

Ipower web hosting - To activate the Debugger from a remote location:

Tuesday, August 28th, 2007

To activate the Debugger from a remote location: 1 Open the Flash authoring application. 2 In a browser or in the stand-alone player, open the published SWF file from the remote location. The Remote Debug dialog box appears. If that dialog box doesn t appear, Flash can t find the SWD file. In this case, right-click (Windows) or Control-click (Macintosh) in the SWF file to display the context menu, and select Debugger. 3 In the Remote Debug dialog box, select Localhost or Other Machine: Select Localhost if the Debug player and the Flash authoring application are on the same computer. Select Other Machine if the Debug player and the Flash authoring application are not on the same computer. Enter the IP address of the computer running the Flash authoring application. 4 When a connection is established, a password prompt appears. Enter your debugging passwordif you set one. The display list of the SWF file appears in the Debugger. Debugging your scripts
In case you need quality webspace to host and run your web applications, try our personal web hosting services.

To enable remote (Web design software) debugging of a Flash movie:

Tuesday, August 28th, 2007

To enable remote debugging of a Flash movie: 1 Select File > Publish Settings. 2 On the Flash tab of the Publish Settings dialog box, select Debugging permitted. 3 To set a password, enter a password in the Password box. After you set this password, no one can download information to the Debugger without the password. However, if you leave the Password box blank, no password is required. 4 Close the Publish Settings dialog box, and select one of the following commands: Control > Debug Movie File > Export Movie File > Publish Settings > Publish Flash creates a debugging file with the .swd extension and saves it alongside the SWF file. The SWD file contains information that allows you to use breakpoints and step through code. 5 Place the SWD file in the same directory as the SWF file on the server. If the SWD file is not in the same directory as the SWF file, you can still debug remotely, but the Debugger ignores breakpoints and you can t step through code. 6 In Flash, select Window > Development Panels > Debugger. In the Debugger, select Enable Remote Debugging from the Options pop-up menu (at the upper right of the panel). 70 Chapter 3: Writing and Debugging Scripts
Searching for affordable and proven webhost to host and run your servlet applications? Go to Linux Web Hosting services and you will find it.

Vps web hosting - To activate the Debugger in test mode:

Monday, August 27th, 2007

To activate the Debugger in test mode: Select Control > Debug Movie. This opens the Debugger. It also opens the SWF file in test mode. Status bar Watch list Display list Code view Debugging a SWF file from a remote location You can debug a remote SWF file using the stand-alone, ActiveX, or plug-in versions of Flash Player. When exporting a SWF file, you can enable debugging in your file and create a debugging password. If you don t enable debugging, the Debugger will not activate. To ensure that only trusted users can run your SWF files in the Flash Debug Player, you can publish your file with a debugging password. As in JavaScript or HTML, it s possible for users to view client-side variables in ActionScript. To store variables securely, you must send them to a server-side application instead of storing them in your file. However, as a Flash developer, you may have other trade secrets, such as movie clip structures, that you do not want to reveal. You can use a debugging password to protect your work. When you export, publish, or test a movie, Flash creates a SWD file that contains debug information. To debug remotely, you must place the SWD file in the same directory as the SWF file on the server. Debugging your scripts 69
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.