flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: SystemManager seems to call addChildAt > out of bounds
Date Thu, 19 Sep 2013 22:29:54 GMT
The Flex framework is a layer over the Flash Player.  The SystemManager is
the framework's wrapper of the Flash 'root'.  You are supposed to only use
Flex APIs and avoid low-level, unwrapped Flash APIs unless you really know
what you are doing.

I can't see anything wrong with the code snippets you've shown us, but it
appears you are launching the alert from within a Tween which is not a
common practice, but should be ok, but if you have a tween doing low-level
Flash API manipulation of the root, that could cause trouble.


On 9/19/13 2:58 PM, "Jiem" <jeanmichel.vilain@gmail.com> wrote:

>I have this other stack trace (before the crash would appear for 2
>reason, now only this one seems to be left as I fixed the Menu):
>RangeError: Error #2006: L'index indiqué sort des limites.
>	at flash.display::DisplayObjectContainer/addChildAt()
>	at
>	at
>	at
>	at
>	at
>	at
>	at
>	at Function/http://adobe.com/AS3/2006/builtin::apply()
>	at
>	at
>	at
>This where how I call Alert.show:
>                    Alert.show(locAlertMessage, locAlertTitle,
>Alert.NONMODAL, GAME, alertHandler);
>GAME is a SkinnableComponent, thus UIComponent
>I have looked into the Flex code, at line 352 of PopUpManagerImpl, he
>decides to addChild like this:
>children = topMost ? smp.popUpChildren : smp;
>if (DisplayObject(window).parent != children)
>     children.addChild(DisplayObject(window));
>Is this buggy...? I'm really looking to hear you, you're the only person
>seems able to bother and who knows his stuff.
>View this message in context:
>Sent from the Apache Flex Users mailing list archive at Nabble.com.

View raw message