Please post the error log. Also, did you listen to error event on SWFLoader or its internal contentHolder. I think it has to be the internal contentHolder.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Michelle Grigg Sent: Monday, April 16, 2007 4:16 PM To: [email protected] Subject: [flexcoders] Re: RangeError on SWFLoader Okay, I stand corrected. I added an error event to the swfloader, and the RangeError STILL occurred. I'm really starting to get ticked off now :-/ --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , John Mark Hawley <[EMAIL PROTECTED]> wrote: > > SWFLoader::load() is an asynchronous call, so you're never going to be able to catch the error in a try block. You should be listening for error events on it instead. > > > > > From: "Michelle Grigg" <[EMAIL PROTECTED]> > > Date: 2007/04/13 Fri AM 09:05:56 CDT > > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > > Subject: [flexcoders] RangeError on SWFLoader > > > > Greetings, > > > > I have been haunted by these fricken #2006 RangeErrors since the start > > of my project though I've been able to fix all but one. > > > > I have a SWFLoader throwing a RangeError, and I can't seem to catch > > the damn thing. The irritating thing is that it's also a very > > intermittent bug so I have no way of telling for sure it will occur > > when first loading my app. > > > > This is the try/catch: > > > > try > > { > > myLoader.load( loadSwfEvent.swfName ); > > } > > catch( e : Error ) > > { > > trace( e.errorID + " " + e.name + " " + e.message ); > > trace( e, ObjectUtil.toString( event )); > > } > > > > It doesn't actually call the catch - it simply prints out the error on > > the console leading me to believe that the error is actually being > > thrown somewhere else, even though the stack trace goes all the way > > back to the SWFLoader class. > > > > I initially thought it to be a timing thing - maybe the swfname wasn't > > being set properly or something, but investigating solutions along > > those lines have been fruitless. > > > > I'm now thinking I should probably be moving the try/catch somewhere > > else, but I would have no idea where. > > > > Any ideas? Similar problems? > > > > Cheers, > > Michelle > > > > > > > > > > -- > John Mark Hawley > The Nilbog Group > 773.968.4980 (cell) >
