Jump to content

destroy and destroy children?


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


  • Recently Browsing   0 members

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