On Wed, Aug 18, 2010 at 3:35 PM, Tom McNeer <[email protected]> wrote: > > > > Pravin, > > Thanks for your suggestions. > > On Wed, Aug 18, 2010 at 9:28 AM, p...@vin Uttarwar <[email protected]> > wrote: >> >> >> >> hopefully youre project is compiling correctly and try to put some traces >> before and after that line. > > It compiles properly, and traces reveal nothing. After the line, of course, > there's nothing to trace because the function fails. >> >> Alos commenting that line removing the error or not? > > You can't simply comment out the line. Its logic wraps the entire body of the > function. The error occurs when the object being tested for null actually is > null. If you comment out that line, you simply move the error down to the > point of where the code attempts to loop over an object that turns out to be > null. >
I think the point is. Sometimes your browser caches an error if the project isn't compiling. Commenting out that line and allowing the error to happen further on ensures that the latest version is really running in your browser. Basically it looks to me like p...@vin is right there should be no such error on this line. I'll add a suggestion of my own try putting a breakpoint in before and just stepping through the code I've seen errors magically disappear this way. If using Flash/Flex Builder ensure there are no errors in your problems tab. Regards, Wesley Acheson
