Jump to content

Recommended Posts

Hey everybody,

First of all big thanks to Pixi.js people for the awesome library. 

I have been using Pixi to develop a simple game and I stumble upon a small bug or I may be doing this wrong. 

So here is the problem, I got a sprite which contains child's sprites.

And I want to destroy it but not the children since I was handling it manually because I need to save the state of each child sprite and then call destroy within them self. So before I calling destroy method I call a custom method on my object,


and then call 

deletingObject.destroy({ children: false, texture: false, baseTexture: false });

but this still destroys all the child within this object, I'm using 


as my Pixi version. and I have attached a screen shot from core developer tools. 


Am I doing the function call wrong or is there something missing. 





Destroy bug.png

Link to comment
Share on other sites

Thanks for the quick reply, Yes you were correct, sourcemaps was messing up the debugs. 

I found the problem, First of all, I thought when call

deletingObject.destroy({ children: false, texture: false, baseTexture: false });

All the children will be still visible on the stage, but little bit digging make me realise that when you delete the parent all the child objects will have null parents hence it won't show on the stage. so it wasn't any bug just me been not fully understanding the scene graph. Anyway, I manage to fix my problem simply by getting all children and setting their parent to the current grandparent.


onDestroy = function () { 
    // Get all the children    
    for (var i = 0; i < this.children.length; i++) {
        // Reset the parent
        this.children[i].parent = this.parent; 
   // Destroy this object
   this.destroy({ children: false, texture: false, baseTexture: false });


Link to comment
Share on other sites

Don't directly assign parent, use the addChild methods of the parent. Otherwise, those objects wont exist in the parent's `children` array and you will have issues. Additionally, your code (when calling destroy) will reset the parent of the children to `null`. The parent property is marked as readonly for a reason :)

Do this instead:

var children = this.removeChildren();

for (var i = 0; i < children.length; ++i) {


That will properly remove the children, properly add them to the parent, then destroy without affecting children/texture/basetexture.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...