HEIDENHAIN iTNC 530 HSCI - Page 1658

1658 HEIDENHAIN Technical Manual iTNC 530 HSCI
Each form definition must be saved under a certain key. The following forms
are currently supported:
 entry_t: "Tools" data form
 entry_p: "Pockets" data form
Special configuration settings:
 entry_t_focus_element:
User interface element from 'entry_t', which has the input focus when the
"Tools" data form opens.
 entry_p_focus_element:
User interface element from 'entry_p', which has the input focus when the
"Pockets" data form opens.
Example of a OEMEntryList.py:
The structure of the keys of the form definitions must be correspond to that
of a Python dictionary, i.e. a list or sequence of keys<-->value pairs. The key
to be specified is the name of the respective user interface element (widget).
The value to be specified is the name of the rule from OEMEntries.py that
defines the data content of the user interface element. The value in the rule
designator entry_tool_name, for example, is transferred to the user interface
element with name entry_TOOL_NAME.
For the form concerned, the two entries entry_x_focus_element define the
user interface element that has the focus when the form opens.
entry_t_focus_element = ’entry_TOOL_NAME’
entry_t = {
’entry_TOOL_NAME’ : entry_tool_name
,’entry_TOOL_T’ : entry_tool_t
,’entry_TOOL_DOC’ : entry_tool_doc
,’entry_TOOLP_P’ : entry_toolp_p
,’checkbutton_TOOL_TL’ : checkbutton_tool_tl
,’comboboxentry_TOOL_TYP’ : comboboxentry_tool_typ
...
}
entry_p_focus_element = ’entry_TOOLP_DOC’
entry_p = {
’entry_TOOL_NAME’ : entry_tool2_name
,’entry_TOOL_T’ : entry_toolp_t
,’entry_TOOLP_DOC’ : entry_toolp_doc
,’entry_TOOLP_P’ : entry_toolp_p
,’checkbutton_TOOLP_ST’ : checkbutton_toolp_st
...
}