RE: [flexcoders] Handling the 32k limit problem

[Matt Chotin]

Are you using <mx:Model source="..."/>?  That's the easiest way to run into this problem.  In Updater 1 we addressed this somewhat by allowing you to have as many objects as you want as long as no one object and its children beat the limit.  So this means you could have many Models, but no one Model could be too big.  In the next release I've gotten this better so that there shouldn't be size limitations on your Models at all.   If you're defining Objects in XML:   <MyObject>   <someProp>    <SomePropType>     etc   Just try not to make the nested structure too big.  With Updater 1 with the exception of using a big Model source I think the 32K limit should be difficult to hit.   Matt   -----Original Message----- From: nts333rd [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 12:34 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Handling the 32k limit problem   I seem to be bumping up against this limit on a regular basis these days, and have been avoiding it by modularizing my application in logical ways. But I'm getting to the point where the refactoring needed is not obvious, and am actually working around this limit. Is there any way to determine exactly where the limit is being reached?  The compiler message refers to two numbers (addresses), for example, "Branch between 42952 and 75725 around line 0 exceeds 32K span".  Will any of the logs help me determine where this "Branch" is? What techniques can I use to avoid this barrier? Any suggestions will be helpful. Tracy