July 2013 8.15 Tool changer 1649
A column definition is evaluated for every read line of the table that provides
the basic information. Linking the line to be evaluated to the column definition
to be used therefore results in exactly one cell value of the view. This also
means that the computing time required for displaying a view increases
significantly with the number of columns defined.
The system automatically tries to translate the ’name’ entries by means of the
'gettext' function. For the cell contents (’value’), however, the rule
’gettext’=’true’ or ’false’ must be used to activate translation.
The language-sensitive *.po files for the gettext function can be created
through PLCtext and must be located in the directory PLC:\Python\LANGUAGE\
. For more information about this, refer to the Python texts help topic in the
PLCtext help.
If the 'gettext' function does not find a translation for a bookmark into the
respective language, the bookmark will automatically be displayed.
HEIDENHAIN therefore recommends using the English text for the bookmark.
This results in the English text being displayed if no translation is found. You
can use the PLC-Text tool for PCs to create the texts for the 'gettext' function.
When defining a column, use the 'type' entry to define the type of column.
The ’check’ column type generates a column with check boxes.
To show a check box, you must define a rule that returns the result ’true’ for
"activated" and ’false’ for "not activated." Alternatively, you can also define a
bitmask function using the '&' operator. This function will return ’true’ for "bit
is set" and ’false’ for "bit is not set." Another possibility is the definition of a
’true-false’ rule. For this type of rule, the value that activates or does not
activate a cell is entered directly.
Example:
(’\\{cell}’, ’true-false’, ’-1’, ’0’)
'-1' activates the cell, '0' means "not activated"
To Next Page
Loading...
