Not sure what on Earth is causing this, but here's the output at times right after the message pointer has been reset. It also has been appearing after all messages have been read, bringing the status of the sub-board up to current. Example follows:
[Current Arguments> msg #3 (0 remaining)] Read cmd -> Next
In main scanSub() loop tmpPtr: 1 total_msgs: 2 is_open: yes
tmpPtr: 1 indices.length: 2 indices[tmpPtr]: 2
Received base: [object MsgBase] ptr: undefined breaks: true
ptr: undefined base.last_msg: 2
Invalid message? base.subnum: 285 ptr: undefined
Uncaught exception from dispMsg(): Invalid message slot
End of scanSub() main loop
tmpPtr: 2 inc: 1
rcChoice() called w/base: topegrpcurrenta ndx: undefined
Using node #: 2
Reopened topegrpcurrenta to check for updates
[Current Arguments> msg #NaN (NaN remaining)] Read cmd ->
Not sure what on Earth is causing this, but here's the output at times right after the message pointer has been reset. It also has been appearing after all messages have been read, bringing the status of the sub-board up to current. Example follows: