Hmm. I am not sure I completely understand the use case, but you can get the current status of a node by it’s “status” property.
Based on your example:
1
2
3
4
5
6
for(vari=0;i<outConnections.Count;i++){
varnode=outConnections[i].targetNode;
varstatus=node.status;
}
There is no event raised when a node changes status, since considering that nodes change status very frequently, that would possibly have a performance impact, especially considering the fact that I haven’t yet found a practical reason for such an event.
I think you have a very special case here 🙂 Would you mind sharing what you want to achieve? Maybe there is another solution to that.