| PathEngine home | previous: | next: |
Interfaces to pathengine, the testbed and objects created by pathengine are implemented as virtual
methods on an abstract base class.
The client application obtains a pointer to the abstract base class and calls functions through this pointer.
The vtable mechanism directs these calls to the correct code within the pathengine or testbed dlls.
To use this mechanism, the c++ binary interface of the client application must be
compatible with the c++ binary interface for pathengine.
On win32 the binary interface is compatible across all major compilers because this is required for COM.
The root interface to PathEngine. All functionality (apart from testbed functionality) is obtained through this interface, or through objects obtained from this interface. | ||
Define a collision shape that can then be used to create multiple agents. | ||
iMesh objects correspond to ground surfaces ('meshes') on which agents can move. | ||
iAgent objects represent the placement of a shape at a position on a mesh. | ||
Represents a state of dynamic collision for an iMesh. | ||
Used to create free standing sets of obstacles, that can then be combined in collision contexts. | ||
A sequence of positions on a mesh. Returned by Pathfinding queries. | ||
Provides information about first contact, in the case of a collision. | ||
Encapsulates a block of content markup that can be saved and loaded to and from persistent store, and instanced for PathEngine's content processing functionality. | ||
Lightweight API object for working with content chunk geometry instantiated at a given position and orientation. | ||
Encapsulates the tiling for a 'federation' of overlapping tiled iMesh instances,
and manages transitions between meshes for
agents moving across the federation. | ||
Encapsulates the tiling applied to 3D source content for tiled 3D content processing. | ||
The client application creates objects deriving from this interface to
pass into
| ||
The client application creates objects derived from this interface to perform customised error handling. | ||
The client application creates objects derived from this interface to receive streamed data from PathEngine. | ||
The client application creates objects deriving from this interface to enable PathEngine to work with a client side representation of surface detail such as a height field for terrain. | ||
The client application creates objects deriving from this interface to
pass into query methods such as
| ||
The client application creates objects deriving from this interface to
pass into visualisation helper functions such as
| ||
An interface class for passing geometry represented in the form of indexed tris and vertices into PathEngine. | ||
An interface class for passing content-side anchor and pinned shape information into PathEngine. | ||
An interface class for passing information about solid source geometry into PathEngine's 3D content processing functionality. | ||
An interface class which can be used to obtain progress updates and display a progress bar during potentially time consuming operations. | ||
Objects derived from this interface are passed in to
| ||
Interface to the PathEngine testbed. | ||
Root interface for dll linkage with PathEngine's 3D content processing functionality. |
| Documentation for PathEngine release 5.24 - Copyright © 2002-2010 PathEngine | next: |