| Age | Commit message (Collapse) | Author |
|---|
|
The pattern seems to show up very often in CollisionInfoBase users
|
|
It's mostly the same thing as LayerContactPointInfo::Iterator.
With some functions inexplicably marked as virtual.
|
|
Clean up the iterator stuff and fix some inaccuracies.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Allows us to get rid of a bunch of local variables that only existed
to force the entire vector to be loaded.
|
|
Turns out it's the equivalent to ContactLayerCollisionInfo.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
And consistency.
|
|
|
|
|
|
|
|
|
|
|
|
The previous name was completely wrong, whoops.
|
|
This reverts commit 42807160cfb33af9f3cf2fa6b0ba98f232208cdb.
It makes searching for NON_MATCHING comment descriptions much less
convenient in most text editors or IDEs, and we want the function
CSV to be the single source of truth for function statuses. Having
a function marked as matching but not built because of a stray #ifdef
would be bad.
|
|
|
|
|
|
|
|
mStaticCompundActorId (#85)
|
|
getDragonItemDropPosition - NON_MATCHING fadd arguments mismatch
|
|
|
|
|
|
|
|
|
|
RigidBodyFactory is right between RigidBodyFromResource and
RigidBodyFromShape functions, and some Factory functions are known
to be in the same TU as RigidBodyFromShape functions.
Some factory functions also use FromShape non-static member functions.
|
|
Also includes a bunch of fixes to the shape and param classes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
