onCollision version with parameters that are "backward compatible" with ...

[doodaddy64]

There is an open question as to how to best handle onCollision in behaviors.

Say two objects A and B collide. T2D has the option to handle onCollision with either the Scene or with the objects themselves. If handling with the scene, you have

myScene::onCollision(%this, %objectA, %objectB, %details)

where you get both objects, of course. If handling with the objects themselves, you have

myObject::onCollision(%this, %objectB, %details)`

The called object is objectA or %this. The question is if handling with behaviors, what do you prefer? Original it was

1) myBehavior::onCollision(%this, %objectB, %details)

That is, to get objectA, you use %this.owner. A recent experiment changed it to

2) myBehavior::onCollision(%this, %parentObjectA, %objectB, %details)

That is, you also get the owner (objectA) directly as %parentObjectA.

Opinions? Don't cares?

The current pull request would switch it back to 1) above. Canceling this pull request would keep it at the new 2).

[MichPerry-GG]

There's a little contention on this pull request. I'd like for other folks to weigh in before we merge or not. Could you create a post in the T2D beginner forum and attach a link to this? I'd like to hear what others think.

[doodaddy64]

Added to forums. http://www.garagegames.com/community/forums/viewthread/133589

[ghost]

So I said yesterday that I wasn't bothered which form the callback took but you know, now that I've had a (much needed) sleep I'm thinking that perhaps the best argument is that behaviors are supposed to act like components OF an object and therefore are supposed to mirror (as much as they can) the callbacks on the parent. In the case of that argument, the commonly-used "onCollision()" and "onEndCollision()" should be as similar as possible so perhaps taking this as a goal, we should remove that extra argument.