Command ‘Properties’¶
Function: This command opens the Properties dialog box for the library selected in the library manager.
Call
- menu
- Context menu of the selected library
symbol in the toolbar of the library manager
Requirement: A library is selected.
Attention
This dialog is intended for library developers. Please use this only if you have profound knowledge of library referencing. In addition, please follow the guidelines for library developers.
See also
- Guidelines for Developing Libraries: guidelines
Dialog box ‘Properties’
Namespace | Namespace of the selected library. By default, this is identical to the library name, unless it was defined explicitly in the project information when the library was created. You can change the namespace for the open project. Example: |
Standard | Library that triggers the placeholder when no other trigger is defined or is possible. Requirement: The selected library is a library placeholder, and therefore the setting is available. Note: Regarding compiler version 3.5.8.0 and later: In the case of library placeholders that have a trigger in the device description and that located in the library manager of the POUs view, the placeholder is always triggered automatically according to the description of the device for which the application is compiled. |
Note
If the selected library is developed in compliance with the “Guidelines for Developing Libraries”, then we do not recommend that you change the following settings.
Selection of version constraint Requirement: The settings are available only if the selected library is not a library placeholder. Note: Container and interface libraries are created automatically with library references with version constraint. As far as possible, do not create libraries that include library references with version constraint. Otherwise, you reference the libraries by placeholders. Edit a placeholder resolution in the Placeholders dialog box. |
|
Specific version |
Note: This option is strongly recommended for container libraries, and it is usually preset for this library type. |
Newest version always |
Note: If a newer library version is available, then the library modules that are actually used can change. This option is strongly recommended for interface libraries, and it is usually preset for this library type. |
Only allow qualified access to all identifiers. | ![]() |
If the current project is referenced as a library by another project. | Note: Changing the following settings makes sense only if you created a library with your project and therefore opened a library project. In this way, the selected library is referenced in the new library. |
Publish all IEC symbols to that project as if this reference would have been included there directly. |
Requirement: A container project is created with a library project. A container library does not implement its own modules, but references other libraries exclusively. It bundles libraries. A container library can be employed sensibly to bundle multiple libraries (in a reference) in a project. This option must be activated for each library reference. Symbolic access to library modules:
Requirement: No container project is created with a library project. Unique symbolic access to the library module: |
Do not show this reference in the dependency tree. |
Warning: If there are compile errors resulting from hidden library errors, then detecting the errors may be difficult.
|
Optional (if the library is missing, no error will be reported). | ![]() |
See also