hi Henrik,

say we have:

trace("getResultSet called", Log.INFO);

unfortunately Log.VERBOSE and other properties continue to be referred by 
mtasc, so error compilation are generated.
Providing a fake log class avoid having additional socket connection and 
calls into swf, allowing to publish it without removing trace points.
That's a workaround for me, please list, tell if you have other ideas.

regards
:)
Jaco - pixeldump

----- Original Message ----- 
From: "Henrik Lindahl" <[EMAIL PROTECTED]>
To: "Open Source Flash Mailing List" <[email protected]>
Sent: Monday, June 12, 2006 9:06 AM
Subject: Re: [osflash] ASDT Logger Tips


> can't you just do "-trace no" ?
>
> /henrik
>
> John Giotta wrote:
>> I ran into a problem just last week and it kind of interesting.
>>
>> I've used the Logger with ASDT projects in the past, but recently I've
>> really had to integrate thorough debugging output. The logger code and
>> tracing has been published to production a SWF still intact. Besides the
>> unusual call to local host (which I understand), the Log class seems to
>> cause a few unwanted effects/defects.
>>
>> The first one is that getURL seems to fail in some instances and other
>> is the Settings Dialog goes completely bonkers.
>>
>> Does anyone have any tips on using the logger in production or should I
>> just avoid all trace calls in the production build?
>>
>> _______________________________________________
>> osflash mailing list
>> [email protected]
>> http://osflash.org/mailman/listinfo/osflash_osflash.org
>>
>
> -- 
> Henrik Lindahl
> Software developer
> Gapminder foundation
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>
> __________ Informazione NOD32 1.1592 (20060611) __________
>
> Questo messaggio  รจ stato controllato dal Sistema Antivirus NOD32
> http://www.nod32.it
>
> 


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

Reply via email to