I'm having a race problem in event structures. I've looked through various forum threads and haven't been able to track down a solution. In the attached vi (labView2015), if you type in a new number for 'X', do not hit enter, and then hit the 'Go' button then the old value for 'X' is used in the event structure. I infer that this is a race problem where having clicked on the 'Go' button has both initiated a task in the event structrue and also set up something in the queue to actually update the value of the variable. That sounds right? This is the simplest example I could make for this problem that has emerged in much larger, more complex vi. All help much appreciated. With thanks! Devon

@MarcDub wrote:Actually, in addition to require a loop around your Event structure, you should configure your event for the GO button for "Value Change" instead of "Mouse down".I should have pointed this out, but I set my event in my snippet to Value Change.

LabVIEW

How to avoid race condition in event loop?

Solved!

@JKSH wrote:
@easyXAFS wrote:

1) throw the whole thing into a while loop and use just 'run'.
or keep using 'run continuous'
Some side notes:

Under most circumstances, "Run Continuously" cooks your CPU. Don't do it!
Under most circumstances, running a while loop without a "wait" cooks your CPU. Remember the wait node!
In this particular case, your CPU was saved by the fact that the event node forces your code to wait.

Worse, RUN CONTINUOUSLY means the only way to stop your VI from running is to use the abort button and that doesn;t leave you a good way to clean up code when your VI should end such as clearing DAQ tasks, closing Com ports, or closing open files.