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

L-force | PLC Designer
Editors in PLC Designer
272 DMS 3.2 EN 02/2011 TD29

The syntax :
• The pragma instruction is enclosed in curly brackets, upper- and lower-case are
ignored: { <Instruction text> }. If it is included in "normal" variable declarations, it
must be set before the terminating semicolon of the declaration.
• Pragmas, which are used in the VAR_CONFIG interface, are set each in a single line
and are not terminated with a semicolon !
• <name>: Name of the parameter list in the Parameter Manager. If the list does not
yet exist, it will be created.
• <key>: Name of the attribute, i.e. column title in the parameter list; e.g. "Name",
"Value", "Accesslevel" etc.; It depends on the definition of the customer specific
parameter list type, which keys can be defined in the pragma. The key definitions
are written separated by space characters, all together enclosed in square
brackets. Regard the syntax for entries in instance lists for arrays, structure resp.
function block components.(see below, 3.).
• <value>: Value of the attribute which is defined by <key>. If <value> contains
empty spaces it must be enclosed in double quotation marks, e.g.
...accessright="read only"...
Note!
The pragma instructions will be effective as soon as the focus is changed, that
means as soon as a precompile is done e.g. via leaving the editor window. Erroneous
inputs will not be messaged until the project is compiled.