Magic xpa Component Properties (Magic xpa 3.x)

« Go Back


Created ByKnowledge Migration User
Approval Process StatusPublished

Magic xpa Component Properties (Magic xpa 3.x)

When you are parked on a component and press Alt+Enter or select Properties from the context menu, the Magic xpa Component Properties dialog box appears.

The dialog box contains the following two sections:

The General Properties section:

  • Revision – A revision number for the component.

  • Project File Name – See the note below.

  • Cabinet File Name – See the note below.

  • Load Immediate – Determines whether or not to load the components together with the project load. If this is selected, then the component will load when the project starts. Otherwise, it will load when a task that uses it is first used (even if none of the component items were used yet). The default value is read from the ECI and can be modified.
    When you are using parallel programs, this property has even more effect. When you start a new context, you can, optionally, re-run the Main Program (if the Initiate Main Program task property is selected).
    Under this circumstance, every new parallel task will reload the component, whether or not the parallel task uses it. So you want to judge carefully how to set Load immediate, depending on how the component is used.

    See also How Do I Optimize Access to a Component?


When running the engine on a Windows operating system, make sure that the path in the project and cabinet file names is defined using a backward slash (\) and not a forward slash (/).

The Settings section:

  • Help File – Path name to the help file. The default location is in the same directory as the ECI. The file name is written in the ECI.

  • Help Key – Keywords to access the help file for a component entry.

The entries in this dialog box are set up by default from the values in the .eci, but you can change most of them.

Particularly important is the Project File and Cabinet File Name fields. Here, they are hard-coded, but when you distribute your application, you will want to use a relative path or logical name so that the host application can find the component properly at the client's site.

Related Topics