Lenze PLC Designer PLC Designer (R3-1) - Manual (Page 383)

L-force | PLC Designer
Menu Commands sorted by Categories

DMS 4.1 EN 03/2011 TD29 381
General:
Namespace: The current namespace of the library is displayed. By default the
namespace of a library primarily is identic with the library name, except another string
has been defined explicitly in the Project Information when creating the library project.
You can edit the namespace anytime here in the properties dialog.
Default library: If a library placeholder is currently selected in the Library Manager, this
field will contain the name of the library which should replace the placeholder, if no
device-specific library is available.
Version:
Here you can configure, which version of the library should be used in the project:
Specific version: Exactly the version entered here (you can select from the list) will be
used.
Newest version always: Always the newest version found in the library repository will
be used, that is the modules actually used might change because a newer version of
the library is available.
Visibility: These settings are of interest as soon as the library gets included that is
referenced by another library: Per default they are deactivated:
Publish all IEC symbols to that project as if this reference would have been included
there directly: As long as this option is deactivated, the components of the current
library - if referenced by another one - can be accessed uniquely by using the
appropriate namespace path (composed of the namespaces of the "father" library and
its own namespace in addition to the modules resp. variable identifier.
Note: Recommendation: The option should only be activated, if you want to use
"container libraries", not containing own modules, but just including other libraries
for the purpose of "packaging" them. This packaging for example allows to include
multiple libraries in a project at once just by including the "container library". In this
case however it might be desired to get the particular libraries on top-level of the
projects' Library Manager, because then the modules can be accessed directly, that is
the namespace of the container library can be left out. And exactly that you can
reach by prospectively activating the option "Publish...".
Hide this reference in the dependency tree: If this option gets activated, the current
library will not be displayed later, when its "father" library is included in a project. This
allows to include "hidden" libraries, however needs careful use, because in case of
library error messages you might have problems to find the causing library.