I have this other stack trace (before the crash would appear for 2 different
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
mx.managers::SystemManag
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 trou
Sorry for my english mistakes, was in a rush when I typed :-)
I wanted to add that what's most bothering is that I could pass through this
code 10 times without crashing. Only sometimes, this exception will happen,
maybe there's some code elsewhere that corrupts this addChild's behavior.
--
View
OK glad to know that addAll calls addAllAt, could explains my troubles.
I have replaced my call to addAll by a for each loop and calls to addItem().
addItem() is safe, isn't it?
I prefer doing this than modifying the Flex SDK.
--
View this message in context:
http://apache-flex-users.246.n4
days. :(
Marcus Wilkinson wrote
> Jiem,
>
> I too was having a few invalid index errors. My specific error was when
> using a Data Group and using addAll() on the Data Provider for that Data
> Group. The issue is here:
> https://issues.apache.org/jira/browse/FLEX-33683
> and the fix
enu. I don't
> believe Menu is designed to be a child component, only a popup.
>
> -Alex
>
> On 9/12/13 7:52 PM, "Jiem" <
> jeanmichel.vilain@
> > wrote:
>
>>Hello
>>
>>I'm working to a project since a long time, I did recently
the
component's creationComplete.
_menu = Menu.createMenu(menuContainer, _menuData, false);
I'm extremely interested by clues regarding this issue. I'm running a stress
test for Faëria: Strategy Card Game, the game uses this code. It's a
client/server architecture (AS3/Jav
