Lenze PLC Designer PLC Designer (R2-x) - Manual (Page 281)

L-force | PLC Designer
Editors in PLC Designer

DMS 3.2 EN 02/2011 TD29 279
Example: The following entry in a VAR_CONFIG window will create entries for
all variables of function block fb1in an instance list varinst1 basing on the
template fb1_templ (which must be already available). For each entry the
index offset, which is predefined by the template, will be increased by 2
(baseindex), the subindex offset will not be modified (basesubindex). Each
entry gets a symbolic name fb1var, which you must edit afterwards in the
Parameter Manager.
VAR_CONFIG
{instance list=varinst1 path=PLC_PRG.fb1
template=fb1_templ baseindex=16#2 basesubindex=16#0 [
name=fb1var ]}
END_VAR
7.3.5 Pragmas for Controlling the Display of Library Declaration Parts
During creation of a library in »PLC Designer« you can define via pragmas which parts
of the declaration window should be visible resp. not visible in the Library Manager
later when the library will be included in a project. The display of the implementation
part of the library will not be affected by that.
Thus comments or any variables declarations can be concealed from the user. The
pragmas {library private} and {library public} each affect the rest of the same line resp.
the subsequent lines, as long as they are not overwritten by the each other one.
Syntax: {library public} The subsequent test will be displayed in the Library Manager.
{library private} : he subsequent test will be not displayed.
Example: See below the declaration part of a library, which is created in »PLC
Designer«. The comment "(* this is for all *)" should be displayed in the Library
Manager after having included the library in a project., the comment "(* but this is not
for all ")" however should not be displayed.