CFG File: Key concepts

The configuration file (.cfg) allows you to customize some elements of Imagenation and of Image a•X. The CFG file is the compiled version of a source configuration file (.src). The CFG file allows you to control which menus, commands, and dialog box options are available for your Imagenation integration, or to define the viewing component for your Image a•X integration.

The following diagram illustrates how the CFG file affects Imagenation or Image a•X, whether they are used in an OLE Automation, in a DDE API, or in a C API integration.

How the CFG file works in your integration

$image\concepts3_shg.gif$

1. OLE Automation, DDE API, and C API integrations can be either 16-bit or 32-bit. An integration with Image a•X can only be a 32-bit application.

2. With OLE Automation, DDE API, and C API integrations, the Imagenation executable (image.exe) is required to run in the background. With ActiveX integrations, you require only Image a•X to be installed and registered on your system.

3. Commands are synchronous. New actions proceed only after the current one is complete.

4. The Spicer DLLs contain user interface elements, such as dialog boxes, file format support, and so on.

5. The configuration file (image.cfg by default) and the initialization file (image.ini by default) affect the state of the Spicer DLLs, and therefore affect the look and feel of Imagenation or Image a•X. These two files must be installed on your system and are required for any integration. (Note: The SRC file is used only to edit and compile the CFG file. It should not be installed with your integration.)

The functionality of Imagenation or Image a•X differs according to the edition of the program being used. The CFG file only affects settings available in the edition of Imagenation or Image a•X that you are integrating.