Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: operator message location

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

ooops...sorry

PB_CMD_kal_output_delayed_op_messages should probably be something more like

global mom_operator_message
global kal_delay_operator_message
global kal_delayed_messages

# clear flag, so later messages are output where specified
catch { unset kal_delay_operator_message} 

# if nothing delayed/saved, return
if {![info exists kal_delayed_messages] ||
    ![llength $kal_delayed_messages]} { return }

# Have saved (delayed) messages - so output them & clean up
# or as appropriate for an array
foreach msg $kal_delayed_messages {
    set mom_operator_message $msg
    MOM_operator_message
}
unset kal_delayed_messages ;# make SURE to clean up
Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled


Re: operator message location

Valued Contributor
Valued Contributor

That did it...Thanks Ken.

Kal.

NX 9.0.3.4 MP12 | PB 9.0.3.2 | NX11.0.2.7 MP13 | PB 11.0.2 | VERICUT 7.3.4

Learn online





Solution Information