Function: The command opens the “Properties” dialog for the library selected in the Library Manager.
Call
-
Menu bar: “Library”
-
Context menu of the selected library
-
Symbol
in the toolbar of the Library Manager
Requirement: A library is selected.
NOTICE
This dialog is intended for library developers. Use this only if you have profound knowledge of library referencing. In addition, follow the guidelines for library developers.
Dialog '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: |
|
“Default”: |
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: For compiler version 3.5.8.0 and higher, the following statement applies in the case of library placeholders with a resolution in the device description that are located in the Library Manager of the “POUs” view. This placeholder is always resolved automatically according to the description of the device that compiles the application. |
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. |
|
|
“Exact version” |
Note: This option is strongly recommended for container libraries, and it is usually preset for this library type. |
|
“Always newest version” |
Note: If a newer library version is available, then the library POUs that are actually used can change. This option is strongly recommended for interface libraries, and it is usually preset for this library type. |
: (selected from list box) Version is integrated into the project.|
“Allow only qualified access to all identifiers” |
|
|
“When the current project is referenced as a library in 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. |
|
“Make visible all IEC symbols in the project if is this reference were directly integrated here.” |
Requirement: A container project is created with a library project. A container library does not implement its own POUs, 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 POUs:
Requirement: No container project is created with a library project. |
|
“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.
|
: Library POUs (and variables) are called in the project only with prepended namespace
paths.
: The contents of the referenced library is accessed uniquely by means of the namespace.
The path name consists of the library name and the unique name (library reference),
and it is prepended to the POU name.|
“Optional (if the library is missing, no error will be reported).” |
|