3D Interop Translationdriver
This document serves to provide an example of flexible code for use by any program that may invoke arbitrary threads to do translations.
Spatial's 3D InterOp requires that all translations be done on the same thread that creates the SPAISystemInitGuard. This complicates programs that may wish to create separate threads for a translation. This is often done in GUI applications that require the main thread to listen for events and handle all translation logic in a separate thread that will not impact the interactivity of the main thread.
Read this tutorial that includes code examples and to learn how:
- One class can manage all translations
- Conversion is done within the boundaries of one and only one SPISystemInitGuard
- To spawn and then destroy a thread in your application so that code management is easier and the translation is localized
- Implement any number of callbacks so that not only one translation code path is needed
- Handle multiple different translations in an application thatdoes not force any of event processing threads to synchronously block for the entire duration of a translation
