Comments on: (As2) swapDepths Vs (As3) setChildIndex

By: From AS2 to AS3 - Where did it go - swapDepths | [mck]

From AS2 to AS3 - Where did it go - swapDepths | [mck] — Wed, 27 Aug 2008 08:00:44 +0000

[...] #2 not possible anymore… if you want a detailed explanation visit dreaming in Flash blog, and read more about swapDepths() in AS3 (it’s explained with a [...]

By: Idoru

Idoru — Tue, 24 Jun 2008 09:52:54 +0000

Well it will throw you an error as there’s no index 42.
if you want you can immediatly change the index of s1 by container.addChildAt(s2,0); which would make s1 top to s2.

By: Reid

Reid — Mon, 23 Jun 2008 18:49:09 +0000

This seems to be a common approach, but I’m skeptical. What happens in the following scenario? Let’s assume container is an empty DisplayObjectContainer…

———————————–
var s1:Sprite = new Sprite();
var s2:Sprite = new Sprite();

container.addChild(s1);
container.addChildAt(s2, 42);

container.setChildIndex(s1, container.numChildren - 1);
———————————–

Now, what are the indeces of s1 and s2?

By: Idoru

Idoru — Fri, 23 May 2008 07:06:54 +0000

Yep that’s what happens, it is better but it also forces you to delete that displayObject manually, as in AS2 you’d just ‘replace’ it

By: JesseJimz

JesseJimz — Fri, 23 May 2008 06:04:47 +0000

So basically, in your example, when swapping the child object at index 0 to index 3, the other children are “pushed” down the stacking order? This IS better than having a movie clip (originally at index 3) killed.

By: Chris

Chris — Fri, 28 Mar 2008 17:24:13 +0000

Thanks