- Derived from
|Full source code is included in the Tinman 3D SDK download.|
Wraps the native libraries of the OpenFlight API.
Using the OpenFlight API in stand-alone mode requires that an application calls the
mgExit functions properly. These functions may only be called once per process. Consequently, the calls to these functions cannot be embedded in the initialization / shutdown scheme of Tinman 3D, which explicitly allows re-initialization after shutdown.
If an application wishes to use the OpenFlight API via OpenFlightModelFormat or OpenFlightSceneDataFormat, it must call the Begin and End methods accordingly. Calls to Begin and End must be balanced and may be nested. The OpenFlight API will only be available between the first call to Begin and the matching call to End. Subsequent calls to Begin can no longer enable the use of the OpenFlight API, as the
mgExit will already have been called by then.
Public / Methods
Adds the default native library search path for the OpenFlight API.
This method uses LowLevel.Is64Bit to choose one of the given relative paths.
The current process is going to use the OpenFlight API.
- See also
The current process is no longer using the OpenFlight API.
Calling this method when there is no matching call to Begin is allowed but has no effect. During shutdown (see TinmanModule.Shutdown), this method is called exactly once.
- See also
Public / Attributes
Allow the OpenFlight API to output error and warning messages?
The OpenFlight API outputs system messages to the standard output stream by default. This behaviour can be disabled. However when doing so, the API sometimes does not return a message for the error of the most recent API call. As a result, the MG class will only be able to provide rudimentary details when throwing exceptions. Set this flag to
true to get system messages and additional exception detail.