1.Import
To import encrypted or unencrypted logic nodes, select "File -> Import -> Logic nodes" in the menu.
Files with the following endings can be imported: ".hsl" and ".hslz".
If errors are determined during the import, e.g., that not all required files are available, the import is cancelled and an error message output.
The import of "unencrypted" modules is NOT project-specific and therefore only has to be carried out once.
If encrypted modules (".hslx" files) are imported, the import of each affected project has to be carried out individually. For this, the unencrypted part of the module has to be overwritten every time.
Files with the following endings can be imported: ".hsl" and ".hslz".
If errors are determined during the import, e.g., that not all required files are available, the import is cancelled and an error message output.
The import of "unencrypted" modules is NOT project-specific and therefore only has to be carried out once.
If encrypted modules (".hslx" files) are imported, the import of each affected project has to be carried out individually. For this, the unencrypted part of the module has to be overwritten every time.
Important
The imported modules are only available after restarting Expert!
1.1.Import of ".hslz" files
A ".hslz" file is a container that can hold several files.
If a corresponding HTML help file is available, this is also imported.
Before import, test if the module is already available. The user can decide if the available module should be overwritten.
For every Global Library available in the ".hslz" file (".hslib" file), the usual dialogue is automatically called up for importing global libraries, and the user has to make the required specifications for this in a dialogue.
If a corresponding HTML help file is available, this is also imported.
Before import, test if the module is already available. The user can decide if the available module should be overwritten.
For every Global Library available in the ".hslz" file (".hslib" file), the usual dialogue is automatically called up for importing global libraries, and the user has to make the required specifications for this in a dialogue.
1.2.Import of ".hsl" files
A ".hsl" file is either an unencrypted complete module or an unencrypted part of an encrypted module. In the latter case, a corresponding ".hslx" file also has to be present in the directory of the ".hsl" file. If an HTML help file also exists for the ".hsl" file, this is imported automatically as well.