aartjan:
tbob was close when he said:
"The reason the wires break is that once the enum structure is set up and wired to the queue functions, that enum structure definition is set in stone in the wiring"
except, that the controlling definition is the data type assigned to the queue and this resides in the tunnel, which in your case carries the queue ref num out of the T/F case controlled by FirstCall?
Here is a quick fix to your dilemma. You must do this in the order giiven:
* change the enum type def for the data, then save and apply, (you'll get the error you showed)
* select the True case of the case structure controlled by the FirstCall?
* delete the tunnel carrying 'queue out' from ObtainQueue to the shift register
* rewire the queue's ref num from 'queue out' from ObtainQueue back to the shift register
* switch to False case
* reconnect the 'queue out' from the new (white) tunnel back to the tunnel from the case structure containing the enqueue, dequeue and destroy ref nums.
The refnum for the queue contains information about the data types in the queue. When the tunnel is connected for the first time, the data type currently in the queue refnum is assigned to the tunnel and any changes to the dat type creates an error. BTW, if you revert the enum type def back and apply it, the error goes away.
John Compton-Smith
