|
The number of bindings should not pushyou over the 32K limit problem. We'd need to see a test-case to debug further, and for this you should probably move over to the support forums: http://www.macromedia.com/cfusion/webforums/forum/index.cfm?forumid=60.
You'll want to post a sample file along with the -generated.as file which you can get by setting keep-generated-as to true in flex-config.xml.
Matt
-----Original Message-----
No, I'm not using <mx:Model at all.
I am using a numberof lightweight, faceless components that communicate using databinding. But we are not talking a large number of bindings at this point, maybe 100?
It seems to be the bindings that push me over the edge. Add one, it breaks, remove it and its ok.
From:Matt
Chotin [mailto:[EMAIL PROTECTED]
Are you using <mx:Model source="..."/>? That's the easiest way torun 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-----
I
seem to be bumping up against this limit on a regular basis these
|
- RE: [flexcoders] Handling the 32k limit problem Matt Chotin
- RE: [flexcoders] Handling the 32k limit problem Tracy Spratt
- Matt Chotin
