Jiem, addItem should be safe, yes. However, I was experiencing a similar (if not the same - im working from memory here) stack when I was removing and adding a single item from the stage once a popup had closed. Updating the SDK fixed my issue. I don't know for sure but addAll / addAllAt _must_ be called internally in the SDK.
This problem was exposed for me very soon after updating the SDK, and I am surprised that more people haven't suffered from this bug. I guess I'm looking to your example to see if it can help other people who may be experiencing the same issue, but only upgrading (or patching) the SDK would confirm this. On 19 September 2013 14:34, Jiem <jeanmichel.vil...@gmail.com> wrote: > 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.2333346.n4.nabble.com/SystemManager-seems-to-call-addChildAt-out-of-bounds-tp2701p2761.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
