Lucas,
 
That *might* remove the 32k error, but not by design.  Anything you do that alters the way the compiler chooses to compile your code is likely to have the side-effect of removing the 32k span error.  However, just because you have the FrameProfilingEnable flag enabled, doesn't mean you're going to remove the possibility of the 32k span error happening again at some future point in time.
 
Hope that clarifies,
 
Steven
 
--
Steven Webster
Technical Director
iteration::two
[EMAIL PROTECTED]
 
Office:  +44 (0)131 338 6108
Mobile: +44 (0)7977 216 223
 
This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies of it, immediately.
 
Please also note that while software systems have been used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened.
 


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Lucas Alfaro
Sent: 10 August 2005 11:40
To: [email protected]
Subject: RE: [flexcoders] 32k problem

 

 Wouldn’t add this parameter FrameProfilingEnable=0 into your mm.cfg bypass this error?

 

L.

 



--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Computer software testing Macromedia flex Development
Software developer


YAHOO! GROUPS LINKS




Reply via email to