API Functions with Special Properties
This page summarizes the API functions that have special properties when used with the API buffer.
API Buffer Control Functions
Some API functions related to API buffer control cannot be stored in the API buffer and are executed immediately, even after calling StartRecordBufferChannel. This includes the following functions:
Functions That Cannot Be Executed from the API Buffer
Some API functions related to engine control or that otherwise use a different data flow channel cannot be stored in the API buffer and are executed immediately, even after calling StartRecordBufferChannel. See Function Calls for Special Processing for a list of these functions.
Functions That Can Only Be Executed From the API Buffer
Some API functions in the ApiBuffer class cannot be executed directly, and can only be executed by first placing them in the API buffer. The following functions will return an error if they are called before calling StartRecordBufferChannel.
Functions That Behave Differently When Executed From the API Buffer
The following functions automatically generate a default size PVT buffer when called for an axis for the first time after starting the WMX3 Engine. However, when these functions are called from the API buffer, a PVT buffer will not be automatically generated. The CreatePVTBuffer function must be called manually before calling these functions from the API buffer.
The following functions automatically generate a default size path interpolation buffer when called for an axis for the first time after starting the WMX3 Engine. However, when these functions are called from the API buffer, a path interpolation buffer will not be automatically generated. The CreatePathIntplBuffer function must be called manually before calling these functions from the API buffer.