Mesh Class Reference

Object subclass for static meshes. More...

Inheritance diagram for Mesh:

Inheritance graph
[legend]
Collaboration diagram for Mesh:

Collaboration graph
[legend]

List of all members.

Public Member Functions

 Mesh (irr::scene::IMesh *mesh, irr::scene::ISceneNode *node, btScalar mass, bool concave=false)
 ctor
 Mesh (irr::scene::IMeshBuffer *meshbuffer, irr::scene::ISceneNode *node, btScalar mass, bool concave=false)
 ctor


Detailed Description

Object subclass for static meshes.

This class, contrary to SharedMesh, performs a deep copy of the mesh data which has the following side effects :

  1. no animation is possible
  2. increased memory usage

It is however useful in some case when some object (eg terrain) don't use a mesh internally but can generate one on demand.

See also:
SharedMesh

Constructor & Destructor Documentation

Mesh::Mesh ( irr::scene::IMesh *  mesh,
irr::scene::ISceneNode *  node,
btScalar  mass,
bool  concave = false 
)

ctor

Parameters:
mesh Mesh data
node Attached scene node
mass Mass of the object
concave whether to create a concave shape
Using concave shapes is recommanded for all environment elements, unless a simpler shape can be used directly (Box or Sphere for example).

Concave shapes should never be used for (even potentially) moving objects.

References Object::init().

Mesh::Mesh ( irr::scene::IMeshBuffer *  meshbuffer,
irr::scene::ISceneNode *  node,
btScalar  mass,
bool  concave = false 
)

ctor

Parameters:
meshbuffer Mesh data
node Attached scene node
mass Mass of the object
concave whether to create a concave shape
Using concave shapes is recommanded for all environment elements, unless a simpler shape can be used directly (Box or Sphere for example).

Concave shapes should never be used for (even potentially) moving objects.

References Object::init().


The documentation for this class was generated from the following files:

Generated on Sat Jul 26 13:58:39 2008 for TFK:GE by  doxygen 1.5.5