In an event structure, we can relate controls to the timeout event. But if we do it this way, we don't get event data node related to the controls. I don't know whether this is a good practice and whether there are potention issues. Please comment. Thanks.

@guangdew1 wrote:In an event structure, we can relate controls to the timeout event. But if we do it this way, we don't get event data node related to the controls. I don't know whether this is a good practice and whether there are potention issues. Please comment. Thanks.A "practice" is what you do. You are talking about a limitation (or feature). Event data nodes only show items that are common to all events of that particular event case, so e.g. "old/new val" is not available if there is also a timeout assigned. If you don't need them, it does not matter if they are there or not.This is often not a problem because you typically only need the new value and you can get that by placing the control terminal inside that event.If you need the specific event data node, create an otherwise empty dedicated event case for the control and fire the timeout event by temporarily setting the timeout to zero via a shift register. Set the timeout back to zero in the timeout event case. If the new value is also needed in the timeout event, leave the terminal inside the timeout event use the newval from the event data node in the specific case.

LabVIEW

Controls that trigger event structure timeout case

Solved!

Author

altenbach, thanks for the explanation which made feel assured that this is an okay way, even though it's not a very common practice. As you mentioned, I don't get the new value from the data node, but if I have the control or local variable inside of the case, I get the new value.