Since the Flex compiler builds AS classes out of our mxml, it has to make some decisions on where to break up the code.
Apparently there are "boundary" conditions where the compiler makes the "wrong" decision. We have found, and had it confirmed by others on this list, that if you simply add more code, even if it is bogus, you can get over that boundary and your app will compile an run again. Ignore the message, add some code, and run the app again. I have also hit a situation where this did not work until I had deleted the files out of the ...web-inf\flex\generated folder, then compiled it again. But usually, 10-15 more lines of code gets me over the hump. If you believe you app is as refactored as is reasonable, give this a try. Tracy -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Fitzpatrick Sent: Monday, April 25, 2005 9:19 PM To: [email protected] Subject: RE: [flexcoders] binding error - from Flex? Tracy - what is that? - Tom At 07:41 PM 4/25/2005, you wrote: >And don't forget to try the "more code" solution. It just worked again >for me the other day. Yahoo! Groups Links Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
