mirror of
https://github.com/photonstorm/phaser
synced 2024-11-23 21:24:09 +00:00
Inconsistency in arcade.collide processCallback param order #667
This commit is contained in:
parent
efc69ff463
commit
24c85dbb35
1 changed files with 1 additions and 1 deletions
|
@ -386,7 +386,7 @@ Phaser.Physics.Arcade.prototype = {
|
|||
* @param {Phaser.Sprite|Phaser.Group|Phaser.Particles.Emitter|Phaser.TilemapLayer|array} object1 - The first object or array of objects to check. Can be Phaser.Sprite, Phaser.Group, Phaser.Particles.Emitter, or Phaser.TilemapLayer.
|
||||
* @param {Phaser.Sprite|Phaser.Group|Phaser.Particles.Emitter|Phaser.TilemapLayer|array} object2 - The second object or array of objects to check. Can be Phaser.Sprite, Phaser.Group, Phaser.Particles.Emitter or Phaser.TilemapLayer.
|
||||
* @param {function} [collideCallback=null] - An optional callback function that is called if the objects collide. The two objects will be passed to this function in the same order in which you specified them, unless you are colliding Group vs. Sprite, in which case Sprite will always be the first parameter.
|
||||
* @param {function} [processCallback=null] - A callback function that lets you perform additional checks against the two objects if they overlap. If this is set then collision will only happen if processCallback returns true. The two objects will be passed to this function in the same order in which you specified them.
|
||||
* @param {function} [processCallback=null] - A callback function that lets you perform additional checks against the two objects if they overlap. If this is set then collision will only happen if processCallback returns true. The two objects will be passed to this function in the same order in which you specified them, unless you are colliding Group vs. Sprite, in which case Sprite will always be the first parameter.
|
||||
* @param {object} [callbackContext] - The context in which to run the callbacks.
|
||||
* @return {boolean} True if a collision occurred otherwise false.
|
||||
*/
|
||||
|
|
Loading…
Reference in a new issue