| DtDynamicTerrainGeometryHandle::DynamicFeature::DynamicFeature |
( |
const DtPoint & |
location, |
|
|
double |
radius |
|
) |
| |
|
explicit |
| DtDynamicTerrainGeometryHandle::DynamicFeature::~DynamicFeature |
( |
| ) |
|
| DtString DtDynamicTerrainGeometryHandle::DynamicFeature::description |
( |
| ) |
const |
|
virtual |
Feature description functions Allows feature to describe itself (for a gui mostly). These can all be called from query callbacks. None of the values returned by these functions have any meaning besides informational.
A description of what is in the feature, how it is setup, configuration, etc.
Implements makVrv::DtDynamicTerrainFeature.
Matching functions. Allow for arbitrary matching against requests, queries, and spatial index subspaces. Setting useOriginalGeometry will match against the geometry without any changes made by this system (i.e. uses the original geometry obtained from the parser).
Implements makVrv::DtDynamicTerrainFeature.
| bool DtDynamicTerrainGeometryHandle::DynamicFeature::isInDefaultState |
( |
| ) |
const |
|
virtual |
| bool DtDynamicTerrainGeometryHandle::DynamicFeature::lastStateWasDefaultState |
( |
| ) |
const |
|
virtual |
Called by the dynamic terrain system in order to notify a feature that it should change its state. The history is an interface into the all of the terrain state changes. This function may be called concurrently from multiple threads.
- Parameters
-
| history | History interface. |
Implements makVrv::DtDynamicTerrainFeature.
| void DtDynamicTerrainGeometryHandle::DynamicFeature::iterateCommands |
( |
const boost::function< void(const makVrv::DtDynamicTerrainChange &)> & |
callback | ) |
const |
|
virtual |
Call the supplied callback on commands which represent the commands a feature can respond to.
This function is designed to be called from a query callback. The purpose of this function is supply a gui or other introspective tool with commands to issue (possibly modified) to this feature or to the terrain. A feature should create commands which they could respond to and would cause them to set themselves to the state they are in now. If there is some command a feature can respond to, outputting it in this function will allow a gui to do things like automatically create a menu with all the possibilities. The commands know the types of the attributes they contain, so the gui will know how to edit the values correctly in order to let the user change the commands before they are issued.
Reimplemented from makVrv::DtDynamicTerrainFeature.
| void DtDynamicTerrainGeometryHandle::DynamicFeature::setToDefaultState |
( |
| ) |
|
| tbb::atomic<bool> DtDynamicTerrainGeometryHandle::DynamicFeature::myDefaultStateFlag |
|
protected |
The documentation for this class was generated from the following file: