Occasionally (too occasionally for me to notice a pattern), the event data node disconnects from the event structure. As far as I know, it's still connected data-wise, but physically floating like a terminal. How do I make it stick to the event structure again?
I'm using LV 2009 right now, but I've seen this behavior in LV 2012 as well. Haven't run across this 2013 - yet.
I'm guessing that this a feature (or unintended behavior) that someone added to the structure at some point and you're somehow triggering a flag which causes it to happen. I don't remember ever running across it during actual developement, but there were some conversations about it on LAVA some years back:
Hmmm, like one of the thread's OP, I don't have that DetachableStructurePartsEnabled=TRUE flag in the ini file for any of the installations that I use. Weird.
Now I want required outputs...
I don't know if I do. I mean when inlineing a VI unwired terminals can perform something like a reverse constant folding, where code is removed because the output isn't needed. I guess I don't mind it being a feature, just as long as it didn't default to on for all outputs.
WOW! I didn't know you could do that on purpose! The only time I ran across it was when opening old code sometimes. Here I thought it was some sort of dire bug that was going to bring a quick and horrible death to my code...
But it's a feature, Huh...
Well it is quite easy to do with an XNode, but it doesn't act like you would want using this method. The XNode Ability GetTerms defines the terminals for the XNode. In there you can say if a terminal is an input or not, and if it is required or not. If you say not an input, and required, the help shows the terminal as required...but you can still run the VI if it isn't wired so it only appears as requried. Outputs can also be optional with this method.
Just to be clear, since people apparently didn't read the thread closely enough - my understanding is that the INI key is not real, but was just a joke. I still think there is a reasonable chance that this is a feature someone purposefully put in and it's getting triggered somehow accidentally (e.g. something in NI's code is modifying the status flags on the structure without taking this into account).