We generally use Macs most of the time, but we also have to use PCs often for specific development or testing.
Using tail trace output for debugging on a Mac is great and we can't live without it, but I never really got around to getting it set up on a PC until yesterday. There's just a couple of steps to get it going.
First, make sure you have the mm.cfg file set up correctly. It'll be located here - if not, create it:
Windows 7 & Vista: C:\Users\username\mm.cfg
Windows XP: C:\Documents and Settings\username\mm.cfg
And make sure it's got the following variables defined:
ErrorReportingEnable=0 TraceOutputFileEnable=1 MaxWarnings=0
Next step is to make sure the file flashlog.txt exists in the following location:
Windows 7 & Vista: C:\Users\username\AppData\Roaming\Macromedia\Flash Player\Logs\flashlog.txt
Windows XP: C:\Documents and Settings\username\Application Data\Macromedia\Flash Player\Logs\flashlog.txt
That will set up the file to receive trace output from Flash Player.
Now to set up the tail command to view output in real time, the first step is to download the Windows Server 2003 Resource Kit Tools installer and run it.
To make things easier, we can also create a batch file to take care of the commands for us. Create a text file somewhere and rename it to "debug-flash.bat" or whatever you want. Edit the batch file in a text editor and add the following lines:
cd <path-to-flashlog-directory> tail -f flashlog.txt
Now double click on the batch file and you're away!
As a side note, if you right click your batch file and choose "create shortcut", you can then right-click the shortcut and select Properties. From this panel you can change some options, including:
- "QuickEdit" mode under the options tab allows easier select/copy/paste etc
Happy debugging 😀