string(35) "/help-for-installation/xpand-module" XPand (C++) module | Xtra Library for Thermo Scientific Amira, Avizo and PerGeos Software

Help for installation
XPand (C++) module


An XPand (or C++) module generally comes as a set of files: one or several pieces of compiled code (with extension .dll for Windows), one resource file (with extension .rc) and some documentation files. It can be packaged with some documentation files. This help page focuses on the local/ directory that contains those files.

Note that an Xtra archive might also contain some additional directories or files, such as sample data, example projects, or tutorial files, that you can save wherever you find it convenient.

Note: no need to have installed the XPand extension to run so-called XPand (C++) modules.

The content of the Xtra local/ directory can be either copy-pasted to the product installation folder - also named AMIRA_ROOT, AVIZO_ROOT, PERGEOS_ROOT - or to an independent custom-defined folder, thereafter named AMIRA_LOCAL.

Installation in the software installation folder:

The custom resource will be accessible to all users of the computer. In case you have several versions of the product installed, the custom resource will only be available in the selected version of the software. In case you upgrade the version of Amira-Avizo Software or PerGeos Software, you will have to re-install the resources. Un-installation is not necessarily simple, as you need to remember which files have been added to the installation folder.

The custom resources are loaded at the startup of the application, so you have to restart the software for the modules to be accessible.

Installation in an independent custom-defined folder:

Each user can decide to connect or not to the directory, that may be shared on the network. The resources will be available from all the installed versions of the product, however compatibility is not guaranteed with all versions (see each Xtra page for its specific compatibility information). It is also simpler, when upgrading the software, to connect to the directory. Again, note that compatibility cannot be guaranteed when upgrading the version of the software.

To use a custom-defined directory (this is also described in the video above):

The custom resources are loaded at the startup of the application, so you have to restart the software for the modules to be accessible.

More information is available in the user's guide, section: Automating, Customizing, Extending.