Wow, how completely infuriating is that...

It seems to be a-ok now.  After much rage..... :)

Thankyou.

--- In flexcoders@yahoogroups.com, "Alex Harui" <[EMAIL PROTECTED]> wrote:
>
> The error is coming from the SystemManager/CursorManager and not the
> SWFLoader.  Try setting showBusyCursor to false on the SWFLoader.
>  
> You won't be able to trap the error as it occurs in an event handler.
>  
> -Alex
> 
> ________________________________
> 
> From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
> Behalf Of Michelle Grigg
> Sent: Monday, April 16, 2007 6:37 PM
> To: flexcoders@yahoogroups.com
> Subject: [flexcoders] Re: RangeError on SWFLoader
> 
> 
> 
> This is the error trace:
> 
> RangeError: Error #2006: The supplied index is out of bounds.
> at flash.display::DisplayObjectContainer/addChildAt()
> 
> at
> mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::r
> awChildren_addChildAt
> <http://www.adobe.com/2006/flex/mx/internal::rawChildren_addChildAt>
> ()[C:\dev\flex_201_gmc\sdk\frameworks\mx\managers\SystemManager.as:1601]
> 
> at
> mx.managers::SystemChildrenList/addChild()[C:\dev\flex_201_gmc\sdk\frame
> works\mx\managers\SystemChildrenList.as:109]
> 
> at
> mx.managers::CursorManagerImpl/mx.managers:CursorManagerImpl::showCurren
> tCursor()[C:\dev\flex_201_gmc\sdk\frameworks\mx\managers\CursorManagerIm
> pl.as:434]
> 
> at
> mx.managers::CursorManagerImpl/setCursor()[C:\dev\flex_201_gmc\sdk\frame
> works\mx\managers\CursorManagerImpl.as:327]
> 
> at
> mx.managers::CursorManagerImpl/setBusyCursor()[C:\dev\flex_201_gmc\sdk\f
> rameworks\mx\managers\CursorManagerImpl.as:400]
> 
> at
> mx.managers::CursorManagerImpl/mx.managers:CursorManagerImpl::progressHa
> ndler()[C:\dev\flex_201_gmc\sdk\frameworks\mx\managers\CursorManagerImpl
> .as:593]
> 
> at
> flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEven
> tFunction()
> 
> at flash.events::EventDispatcher/dispatchEvent()
> 
> at
> mx.core::UIComponent/dispatchEvent()[C:\dev\flex_201_gmc\sdk\frameworks\
> mx\core\UIComponent.as:8323]
> 
> at
> mx.controls::SWFLoader/mx.controls:SWFLoader::contentLoaderInfo_progress
> EventHandler()[C:\dev\flex_201_gmc\sdk\frameworks\mx\controls\SWFLoader.
> as:1673]
> 
> If it needs to be added to the internal content holder of the
> SWFLoader, which property do I add it to? There is no property listed
> in the Lang Ref called contentHolder...?
> 
> --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
> , "Alex Harui" <aharui@> wrote:
> >
> > 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: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
> [mailto:flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
> ] On
> > Behalf Of Michelle Grigg
> > Sent: Monday, April 16, 2007 4:16 PM
> > To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> 
> > 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 flexcoders@yahoogroups.com
> <mailto:flexcoders%40yahoogroups.com>
> <mailto:flexcoders%40yahoogroups.com>
> > , John Mark Hawley <mark@> 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" <michellejg@>
> > > > Date: 2007/04/13 Fri AM 09:05:56 CDT
> > > > To: flexcoders@yahoogroups.com
> <mailto:flexcoders%40yahoogroups.com>
> <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)
> > >
> >
>


Reply via email to