Accessibility

Table of Contents

  1. Introduction
  2. Installing the Flash Debug Player
  3. Configuring the Flash Debug Player
  4. Flash Player Tracing()
  5. Flex’s XMLObjectOutput
  6. Command-Line Debugging
  7. Configuring the Flex Server for Client Debugging
  8. Configuring and Running Flex’s Client ActionScript Debugger (fdb)
  9. Other Considerations
  10. In Conclusion

Debugging Client-Side Code in Flex Applications

Command-Line Debugging

Flex’s ActionScript command-line debugger (fdb) allows you to view, in real time, the properties and characteristics of all ActionScript code that comprises an MXML file executing in the Flash Debug Player. Use the fdb to set break points in AS code, step through those break points, and view application trace data as a SWF runs in the browser.

When Flex links and compiles ActionScript, SWCs, and MXML, it produces two generated files for each compiled MXML file. The first file, compiled_mxml_filename.1, contains the class definition of the class associated with the compiled MXML. This file contains the SWF init() function, event handlers, as well as any other ActionScript code required to implement the MXML. You can set breakpoints on most functions in this file except the event handlers.

Note, you can set breakpoints for the event handlers only in the original MXML file. The second file, compiled_mxml_file_name.2, contains the deferred instantiation entry for the MXML mapped class, if any.

Page 6 of 10
Previous Page
Next Page