Because it
uses the stdcall convention, it can be used in a variety of languages. |
|
NWCreate has 2 components: An exporter API:LiNwcAPI
for exporting NWD files from a 3rd
party app. & a loader
(LiNwcLoader) for reading data from |
|
Files and
converting to NWD scenes. |
|
LiNwcAPI functions must be called when writing an
exporter from third party software. They should not be called when writing a
file loader |
|
Loaders are
registered with NavisWorks by adding a string value to the "NWCreate
Loaders" key in the registry. NavisWorks loads a loader DLL on demand
when a file supported by the loader is opened. |
|
Your application
should link with nwcreate.lib from the lib directory. The implementation of
the API is in nwcreate.dll from the release directory. You should distribute
this DLL with your application. |
|
LiNwcLoader |
|
Represents an object
that can read data from a file and convert it to a NavisWorks scene.
NavisWorks invokes a loader whenever a user opens a file. Loaders are compiled into DLLs with a single well defined entry point. |
|
Loaders are
registered with NavisWorks by adding a string value to the "NWCreate
Loaders" key in the registry. The key exists under both
HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER. |
|
NavisWorks loads the
loader DLL on demand when a file supported by the loader is opened. The
capabilities of the loader are described to NavisWorks using a configuration
file. The configuration file must be in the same directory as the loader and
have the same name, but with a ".txt" extension. Your loader dll
and config file are all that need to be distributed. |
|