Jump to content

overlapHandler caled with parameters in wrong order?


Leep
 Share

Recommended Posts

Is it just me or does physics.arcade.overlap end up calling the overlapHandler with the object1/object2 parameters in the wrong order if object 1 is a group and object2 is a sprite?  I'm looking the code in World.js (http://docs.phaser.io/World.js_.html), and overlap calls collideHandler, which in turn calls collideSpriteVsGroup if object1 is a group and object2 is a sprite, but for that one specific case it passes the parameters to collideSpriteVsGroup in the order object2, object1 instead of object1, object2 like in all other cases.  Is this intentional?

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