The callback procedures defined for the component tagout displays are decomposed on the basis of how
and why they are executed. Those described in subsection 5.3.6.1 are callbacks that are called either
one time during load, one time during unload, or twice per second. These are configuration callbacks that
support the physical appearance of the display rather than the operational function provided by the
display. The callbacks in subsection 5.3.6.2 are executed when the operator interacts with the tagout
control panes and applies or removes tags from the components.
5.3.6.1 Timer/Load/Unload Callbacks
These callbacks are used to configure the dynamic elements of the display for first appearance, for
clean-up in preparation for the display to be generated again in the future, and to update any dynamic
elements on the display that may change state while the display is being viewed.
5.3.6.1.1 Procedure sc_tag_load
The sc_tag_load procedure is defined as a realize callback on each component tagout display and is
simply a call to local function ClearTagOut (subsection 5.3.6.1.3) which updates the tagout control panes
with the current tagout states and disables all buttons on each tagout soft control.
5.3.6.1.2 Procedure sc_updatet
Each indication of tag state and last known soft control state required for display on the component tagout
displays is presented in a table, as noted in subsection 5.2.1.6.1. Since the tag state and soft control state
of each component can change at any given moment, either via the tagout controls on the display being
viewed or by SD soft control in another division, the table data must be updated continuously. The
PtTimer widget located in the header of each display provides for execution of callbacks every
half second. Procedure sc_updatet is defined as an activate callback on the PtTimer widget.
The callback procedures defined for the component tagout displays are decomposed on the basis of howand why they are executed. Those described in subsection 5.3.6.1 are callbacks that are called eitherone time during load, one time during unload, or twice per second. These are configuration callbacks thatsupport the physical appearance of the display rather than the operational function provided by thedisplay. The callbacks in subsection 5.3.6.2 are executed when the operator interacts with the tagoutcontrol panes and applies or removes tags from the components.5.3.6.1 Timer/Load/Unload CallbacksThese callbacks are used to configure the dynamic elements of the display for first appearance, forclean-up in preparation for the display to be generated again in the future, and to update any dynamicelements on the display that may change state while the display is being viewed.5.3.6.1.1 Procedure sc_tag_loadThe sc_tag_load procedure is defined as a realize callback on each component tagout display and issimply a call to local function ClearTagOut (subsection 5.3.6.1.3) which updates the tagout control paneswith the current tagout states and disables all buttons on each tagout soft control.5.3.6.1.2 Procedure sc_updatetEach indication of tag state and last known soft control state required for display on the component tagoutdisplays is presented in a table, as noted in subsection 5.2.1.6.1. Since the tag state and soft control stateof each component can change at any given moment, either via the tagout controls on the display beingviewed or by SD soft control in another division, the table data must be updated continuously. ThePtTimer widget located in the header of each display provides for execution of callbacks everyhalf second. Procedure sc_updatet is defined as an activate callback on the PtTimer widget.
正在翻譯中..
