swapChild implemented via addChildAt

[ccoenen]

swapChild was currently not available, i implemented it via two simple addChildAt calls. This would also close #287.

[ccoenen]

I also have a different approach, re-knitting the linked list, but somehow i had an error somewhere halfway through that created an infinite loop. If you're interested in that, you can have a look at it right here: ccoenen@ef34c55

[englercj]

I'd be interested to compare this with phaser's swap implementation:

https://github.com/photonstorm/phaser/blob/dev/src/core/Group.js#L232

[xixixao]

Hey guys, I am trying to figure out, what is the way to handle order of sprites in PIXI? My particular situation: I have 10000 sprites and say 100 others which I need to place in front of specific sprite from the big group. The only thing I can think of now is to keep track of indices of the 10000 sprites and use addChildAt. Is there a way to addChildAfter(sprite1, sprite2) - that would be all I need, I think.

[drkibitz]

An insertBefore and an insertAfter would be useful, but if there are already internal references (linked list) then I don't believe building on those methods for implementing a fast swap is needed.

I guess my problem is that the linked list implementation is a bit confusing in regards to property names, and I have unfortunately tried to avoid it. I would love to have exposed properties such as firstChild, lastChild, previousSibling, nextSibling, and parent. I think the only one that exists like this is parent, while finding the rest of those will require a bit longer stint of reverse engineering. I remember reading in another thread that both a doubly linked list and a children stack are implemented for different reasons. From my point of view I would never use the stack to manipulate order if there is already a linked list. What is the benefit of the stack other than looping?

[englercj]

Implemented #431

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.