Jump to content

destroy and destroy children?


ForgeableSum
 Share

Recommended Posts

That looks like a bug in docs generation. Image inherits from PIXI.DisplayObject, then the Phaser component stuff comes in and shadows the Image's inherited destroy method with Phaser's own. I'd believe the second one, in this case.

 

Phaser.Component is how Rich et. al. reduced code duplication in the codebase recently (2.2? 2.1?). It's a bunch of prototypes that get mixed in to the standard classes.

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.

Guest
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.

Loading...
 Share

  • Recently Browsing   0 members

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