[ODE] ODE 0.50 distribution

[John Miles]

Yes, I do keep the mesh geometry around, but it's owned by the physics
representation.  It's not directly accessible from, say, the renderer, where
I use it to draw diagnostic geom wireframes.

If I were into breaking encapsulation, I would have just accessed the
triangles directly, without calling dGeomTriMeshGetTriangle() at all.  It
didn't make sense to include an API function to access the mesh's triangle
data but not its triangle count.

-- jm

> > Without this, there's no way for the app to tell what range of Index
> > parameters can be passed to dGeomTriMeshGetTriangle() without violating
> > encapsulation or keeping redundant polygon-count variables around.
>
> Seeing as how you need to keep the entire vertex and index data set
> around (ODE doesn't for you), keeping this "redundant" count seems like
> an inconvenience not worth mentioning.
>
> Cheers,
>
> 			/ h+
>
>