@Niels, Thanks for the feedback, I'l try that tonight. Using 'tail' as you 
described would be very useful.

I did read about setting up the mm.cfg in the documentation, but I had thought 
'TraceOutputFileEnable" was only if you wanted to log the the trace() outputs 
to file, as opposed to displaying them on top of the flash movie? So I was 
mistaken in assuming the default behaviour for trace() is to display text on 
the top layer of the movie? 
Izak


Original Message ----
From: Niels Wolf <[EMAIL PROTECTED]>
To: Open Source Flash Mailing List <[email protected]>
Sent: Tuesday, August 12, 2008 9:42:12 AM
Subject: Re: [osflash] Am I overlooking any crucial tools?

Re: [osflash] Am I overlooking any crucial tools? Where to get:
http://www.adobe.com/support/flashplayer/downloads.html

Additional troubleshooting for OSX:
http://kb.adobe.com/selfservice/viewContent.do?externalId=4aa64290

The debug player requires you to edit the debugger config ("mm.cfg") file:
TraceOutPutFileName={for location see below}/flashlog.txt
ErrorReportingEnable=1
TraceOutputFileEnable=1
MaxWarnings=100

You can find the "mm.cfg" at:
Windows 95/98/ME/2000/XP C:\Documents and Settings\{username}\Application 
Data\Macromedia\Flash Player\Logs\
Windows vista c:\USERS\{username}\AppData\Roaming\Macromedia\Flash Player\Logs\
Macintosh OS X /Library/Application Support/macromedia/
Linux /home/{username}/.macromedia/flash_player/logs/ 

The "flashlog.txt" should be created at (rights set to READ/WRITE):
Windows 95/98/ME/2000/XP: C:\Documents and Settings\{username}\Application 
Data\Macromedia\Flash Player\Logs\flashlog.txt
Windows Vista: C:\Users\{username}\AppData\Roaming\Macromedia\Flash 
Player\Logs\flashlog.txt
Linux: home/{username}/.macromedia/Flash_Player/Logs/flashlog.txt
Macintosh OS X: /Users/{username}/Library/Preferences/Macromedia/Flash 
Player/Logs/flashlog.txt

More information:
http://livedocs.adobe.com/flex/201/html/logging_125_01.html

You can watch the debug output at the console by using "tail": 
tail -f {for location so above}Logs/flashlog.txt



On 8/11/08 10:01 PM, "izak marais" <[EMAIL PROTECTED]> wrote:


Hi everyone, 
Well after fresh install and a reboot my flash player works again. I´ve 
replaced /usr/lib/flashplugin-nonfree/libflashplayer.so with the debugger 
libflashplayer.so from the SDK and it still works. I can also run swf's in the 
standalone player. I've started compiling actionscript tutorials using mxmlc. 

However I can't get trace() to work (in either the plugin or the standalone). 
Trace instructions are simply ignored. I've even tried running the compiler 
with the debug=true flag, but as expected that does not influcence trace(). 
What could I be doing wrong?

Here is a minimal example (contents of file HelloWorld.as:

package { 
    import flash.display.Sprite; 
    import flash.text.TextField; 
     
    public class HelloWorld extends Sprite { 
         
        public function HelloWorld() { 
            var display_txt:TextField = new TextField(); 
            display_txt.text = "Hello World!";                            
//displays text
            trace("attempting to trace something else")         //does nothing
            addChild(display_txt); 
        } 
    } 
} 

The compiler is invoked:
mxmlc -benchmark=true HelloWorld.as

regards,
Izak

----- Original Message ----
From: Martin Wood-Mitrovski <[EMAIL PROTECTED]>
To: Open Source Flash Mailing List <[email protected]>
Sent: Thursday, August 7, 2008 9:29:49 AM
Subject: Re: [osflash] Am I overlooking any crucial tools?



izak marais wrote:
> Thanks for the feedback. I am glad that the compiler will work easier 
> than the player. Ubuntu indeed uses the nspluginwrapper and I previously 
> had the flash9 player working, however by following the first part of 
> the  SDK installation instructions (uninstall falsh player plugin and 
> replace it with the debugger version distributed as part of the SDK) I 
> have managed to break it.
> 
> However, the stand-alone-player (i.e. not the browser-plugin) 
> distributed with the SDK runs fine. So is it really necessary to have 
> the browser-plugin-player be the debugger version? Does the rest of the 
> SDK depend on this? Or could I use the stand-alone-player for debugging 
> and stick with the standard player?

just use the standalone.


actually thats one thing that bothers me about FlexBuilder is that it defaults 
to generating html wrappers and launching them in the browser without any 
preferences to change it for new projects.

what i find strange is that they could have easily integrated the player into 
an 
eclipse view either via some JNI stuff to directly host the plugin or via the 
browser component, after all Adobe should know their own technology....anyway, 
im rambling about FlexBuilder which isn't free or open source so not really 
appropriate :)


_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org


      
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to