In C something like that would generate tons of errors but I don't know what is a TObject and how it is handled by Pascal, so tell me when you have time .
In the fall of 1972 President Nixon announced that the rate of increase of inflation was decreasing. This was the first time a sitting president used the third derivative to advance his case for reelection.
-=Hugo Rossi=-
Sure we can add functionality for undefining a collision, but is it really neccessary? I would use a global variable instead and test it in oncollision if the actions should trigger or not. Please describe a scenario where you would use such a feature.
The most important thing I can think of is performance. When you for example have a large level that you can split up in arena's, you only want to check collision with objects that are in the area you're currently in.
BTW: I have thought about a smart way to define/undef collisions (dunno if was the same Ville was thinking about). What about a 32x32 2D-Array to be used as a table? 0 would mean "do not call collision" and the other values (1, 2 and so on) can be used as a flag to say what action should be taken.
But yes I do agree Undefining a collision is something not common. The only apply I can find is the same of "CollisionsEnabled" in the App.State component, previded that you want that just some collisions are disabled. And let's say something like "permanent invulnerability" towards something (but I know that can be made using variables as flag, too!)
I was just speculating about it...
In the fall of 1972 President Nixon announced that the rate of increase of inflation was decreasing. This was the first time a sitting president used the third derivative to advance his case for reelection.
-=Hugo Rossi=-