On 15 juil. 06, at 10:52, Greg Ewing wrote:
While you're reworking the ODE stuff, is there any chance of relaxing the restriction that an ode.Body be a direct child of an ode.World?
In the new implementation I currently writing ode stuff will be integrated to the soya core. Every Body (fka Volume) will have the abilities to be (or not) ODE managed and every World maybe have ODE world property.
All ODe feature will be off be default and are activated by simple methode such as your_body.enable_ode(). As class specific to ODE will disappear and Activation will be process a separated of the creation of the object this restriction will go away. Body will automagicly go up the tree looking for a World with ODE support enabled (However you can also specify the world you want he join)
You look to have good experience of soya with ODE and many good any about what to improve. I may be a good idea to have a little conversion on irc or jabber ([EMAIL PROTECTED])
marmoute _______________________________________________ Soya-user mailing list [email protected] https://mail.gna.org/listinfo/soya-user
