pyode-user

[Pyode-user] TriMesh API

[Ethan Glasser-C. <gl...@cs...>]

Hi,

I've been looking at the TriMesh API. Expected use is something like:

    d =3D ode.TriMeshData()
    d.build(verts, faces)
    g =3D ode.GeomTriMesh(d, space)

It seems to me it would be more pythonic to use something like:

    d =3D ode.TriMeshData(verts, faces)
    g =3D ode.GeomTriMesh(d, space)

Why is it this way? Just to mime the ODE API better?

Ethan

Re: [Pyode-user] TriMesh API

[Matthias B. <mat...@gm...>]

Ethan Glasser-Camp wrote:
> I've been looking at the TriMesh API. Expected use is something like:
> 
>     d = ode.TriMeshData()
>     d.build(verts, faces)
>     g = ode.GeomTriMesh(d, space)
> 
> It seems to me it would be more pythonic to use something like:
> 
>     d = ode.TriMeshData(verts, faces)
>     g = ode.GeomTriMesh(d, space)
> 
> Why is it this way? Just to mime the ODE API better?

Yes, the build() method just wraps the dGeomTriMeshDataBuildSimple() 
function. But I don't have any objections of providing functionality to 
do that in the constructor as well.

- Matthias -