[ODE] New Joints format

George Birbilis birbilis at kagi.com
Wed Feb 7 09:51:07 MST 2007

I suggest using #include at the correct positions (e.g. at the last line of
that enum you mention). Then at the include files (empty stubs at the
official distro) you could add your stuff

George Birbilis (birbilis at kagi.com)
Microsoft MVP J# 2004-2007
Borland "Spiriti of Delphi"
QuickTime QTVR ActiveX .NET Delphi

-----Original Message-----
From: ode-bounces at ode.org [mailto:ode-bounces at ode.org] On Behalf Of Bill
Sent: Wednesday, February 07, 2007 10:27 AM
To: ODE Mailing List (E-mail)
Subject: [ODE] New Joints format

Hi All,

Often the best way of achieving a particular effect (best as in  
stable and quick) is to create a new joint. Whilst this isn't  
particularly difficult in the current ODE (although some extra  
documentation would help) once you've written your custom joint it is  
a real pain to keep on top of code revisions because you need to keep  
private copies of 5 different files and repatch the new ones. It  
seems to me that we could probably come up with a format that allows  
just a single custom_joints.cpp and custom_joints.h file - preferably  
that can be defined at ./configure time. Certainly all the changes to  
joint.cpp, joint.h, ode.cpp would be fine. The changes in objects.h  
would also be fine since anyone using a custom joint can probably  
cope with being careful not to use the non-public interface to their  
new joint. The only real problem is common.h since you need to add  
extra joint types and the easiest way I can think of to fix that is  
to include a few dJointTypeUser1, dJointTypeUser2, dJointTypeUser3  
definitions at the end of the enum. There isn't really any overhead  
associated with doing that - I'd add 100 extra definitions to make  
sure there are enough for anyone (and the enum will still fit into a  
char if that is what your compiler wants to do).

ODE mailing list
ODE at ode.org

More information about the ODE mailing list