Editing the mm.cfg file

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 Flash Player 10.1 and later on several operating systems:

Operating system

Create file in …

Macintosh OS X

Flash Player first checks the user’s home directory (~). If none is found, then Flash Player looks in /Library/Application Support/Macromedia

Windows 2000/XP

%HOMEDRIVE%\%HOMEPATH%

The default value is “c:\Documents and settings\username”.

Your system administrator might map the home directory to a shared network drive. In that case, check with your system administrator to determine how to configure your debugger Player.

Windows Vista Windows 7

%HOMEDRIVE%\%HOMEPATH%

The default value is “c:\Users\username”.

Your system administrator might map the home directory to a shared network drive. In that case, check with your system administrator to determine how to configure your debugger Player.

Linux

/home/username
On Microsoft Windows 2000, the default location of the mm.cfg file for earlier versions of Flash Player was \.

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.

PolicyFileLog

Enables the logging of policy file messages.

Set PolicyFileLog to 1 to log policy file messages. The default value is 0.

For more information on using policy file logs, see Log file location.

PolicyFileLogAppend

Lets you save the contents of the policy file log file.

Set the PolicyFileLogAppend property to 1 to save previous policy file log entries. The default value is 0.

If PolicyFileLogAppend is not enabled, each new root-level SWF clears the log file. If PolicyFileLogAppend is enabled, the previous contents of the log file will always be kept, and the log file will grow at the end.

If many different root-level SWF files are loaded during your testing, you will probably want to enable PolicyFileLogAppend. However, if you enable PolicyFileLogAppend, you will probably need to manually rename or delete the log file from time to time, since otherwise it will grow to a large size, and it will be difficult to determine where previous output ends and new output begins.

For more information on using policy file logs, see Policy file logging.

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