#22 Change in OgreOde API?

1.6.0
closed-accepted
Andy
5
2008-11-26
2008-11-25
No

I'm using OgreOde. I used to be able to do this:

Code:
testSpace.collide(ray)

where testSpace is an odeSpace object and ray is a RayGeomtry object.

However, I now get a complaint about the signature not matching:

Python argument types in
HashTableSpace.collide(HashTableSpace, RayGeometry)
did not match C++ signature:
collide(struct HashTableSpace_wrapper {lvalue}, class OgreOde::CollisionCallback * colCallback, class OgreOde::Geometry * geometry,
bool useInternalCollisionFlag=True)
collide(class OgreOde::HashTableSpace {lvalue}, class OgreOde::CollisionCallback * colCallback, class OgreOde::Geometry * geometry,
bool useInternalCollisionFlag=True)
collide(struct HashTableSpace_wrapper {lvalue}, class OgreOde::CollisionCallback * colCallback, class OgreOde::Space * space)
collide(class OgreOde::HashTableSpace {lvalue}, class OgreOde::CollisionCallback * colCallback, class OgreOde::Space * space)
collide(struct HashTableSpace_wrapper {lvalue}, class OgreOde::CollisionCallback * colCallback, bool useInternalCollisionFlag=True)
collide(class OgreOde::HashTableSpace {lvalue}, class OgreOde::CollisionCallback * colCallback, bool useInternalCollisionFlag=True)

Is the simpler version of the method (which does not require a CollisionCallback object) no longer being wrapped?

Discussion

  • Andy

    Andy - 2008-11-26

    Due to change (improvement) in wrapper code means that in this case the function name changed to collideVoid_1 Clearly I need to fix this in the doc strings...

     
  • Andy

    Andy - 2008-11-26
    • milestone: --> 1.6.0
    • assigned_to: nobody --> andy_miller
    • status: open --> closed-accepted
     

Log in to post a comment.