LabVIEW
Event Structure Basics
Lock panel is not really detectable here, because the event completes in nanoseconds. You would run into problems if the event is not reachable or contains interactive code that prevents completing the event case.
@cwhw112 wrote:
Creating multiple event specifiers is an OR (if 1, 2, OR 3). Is there a way to make an AND?
****************************************************************************************************************************************************
using a boolean button value change, if the mechanical action is latch, it only executes the event once even though the button goes high, then low (2 value changes), whereas if the mechnical action is switch (even switch until released) it executes the even on every value change (can be seen in attached vi - increment only 1 per latched button push). Why is this?
****************************************************************************************************************************************************
all events are supposed to be captured and queued into a FIFO
my program increments Numeric when Do some work? is pressed and should turn on the Boolean 2 indicator the first time Numeric changes value but never does. Why is this?
Value change events are not triggered by writing to an indicator (they are mainly meant for UI interaction). You'll need to use a Value(signalling) property node.
