????????? You use the settings in the mm.cfg text file to configure the debugger version of Flash Player. These settings also affect logging of trace() output in AIR applications running in the ADL debugger. If this file does not exist,you can create it when you first configure the debugger version of Flash Player. The location of this file depends on your operating system.
The following table shows where to create the mm.cfg file for several operating systems:
| Operating system |
Create file in ***
|
| Macintosh OS X |
/Library/Application Support/Macromedia |
| Windows 95/98/ME |
%HOMEDRIVE%%HOMEPATH% |
| Windows 2000/XP |
C:Documents and Settingsusername |
| Windows Vista |
C:Usersusername |
| Linux |
/home/username |
?????
??
On Microsoft Windows XP,the default location was Documents and Settings
user_name. On Microsoft Windows 2000,the default location was . For earlier versions of Flash Player on Windows XP and 2000,the location of the mm.cfg file was determined by the
HOMEDRIVE and
HOMEPATH environment variables.
The following table lists the properties that you can set in the mm.cfg file:
| Property |
Description |
| ErrorReportingEnable |
Enables the logging of error messages. Set the ErrorReportingEnable property to 1 to enable the debugger version of Flash Player to write error messages to the log file. To disable logging of error messages,set the ErrorReportingEnable property to 0. The default value is 0. |
| MaxWarnings |
Sets the number of warnings to log before stopping. The default value of the MaxWarnings property is 100. After 100 messages,the debugger version of Flash Player writes a message to the file stating that further error messages will be suppressed. Set the MaxWarnings property to override the default message limit. For example,you can set it to 500 to capture 500 error messages. Set the MaxWarnings property to 0 to remove the limit so that all error messages are recorded. |
| TraceOutputFileEnable |
Enables trace logging. Set TraceOutputFileEnable to 1 to enable the debugger version of Flash Player to write trace messages to the log file. Disable trace logging by setting the TraceOutputFileEnable property to 0. The default value is 0. |
| TraceOutputFileName |
Note: Beginning with the Flash Player 9 Update,Flash Player ignores the TraceOutputFileName property and stores the flashlog.txt file in a hard-coded location based on operating system. For more information,see Log file location. Sets the location of the log file. By default,the debugger version of Flash Player writes error messages to a file named flashlog.txt,located in the same directory in which the mm.cfg file is located. Set TraceOutputFileName to override the default name and location of the log file by specifying a new location and name in the following form: On Macintosh OS X,you should use colons to separate directories in the TraceOutputFileName path rather than slashes. TraceOutputFileName=<fully qualified path/filename>
|
The following sample mm.cfg file enables error reporting and trace logging:
ErrorReportingEnable=1
TraceOutputFileEnable=1
Log file location
The default log file location changed between the initial Flash Player 9 release and the Flash Player 9 Update. In the initial Flash Player 9 release,the default location was the same directory as the mm.cfg file and you could update the log file location and name through the TraceOutputFileName property.
Beginning with the Flash Player 9 Update,you cannot modify the log file location or name. The filename is flashlog.txt,and its location is hard-coded,depending on your operating system. The following table shows the flashlog.txt file location:
| Operating System |
Log file location |
| Windows 95/98/ME/2000/XP |
C:Documents and SettingsusernameApplication DataMacromediaFlash PlayerLogs |
| Windows Vista |
C:UsersusernameAppDataRoamingMacromediaFlash PlayerLogs |
| Macintosh OS X |
/Users/username/Library/Preferences/Macromedia/Flash Player/Logs/ |
| Linux |
/home/username/.macromedia/Flash_Player/Logs/ |
