Stop compiling array when paused

[Jammin]

In the vi below, while waiting for user input I would like the vi not to be processing additional data. The result now is that instead of one row of results per iteration I get multiple depending on how long I wait.

[Broken_Arrow]

You need some data dependency between the File Dialog and that first For loop. Wire the File Dialog's error output to the edge of the For Loop, and that will prevent it from spinning while you wait for the user to react.

Message Edited by Broken Arrow on 04-13-2010 01:48 PM

[Broken_Arrow]

I may have misunderstood your question. What exactly are we waiting on? The Pause button? From True to False?

[Jammin]

When the vi runs, it pauses automatically at each iteration, where it should wait until a user corrects the cursor position on the graph. It is this data that should be saved, and it is, the problem is that in the output file multiple rows of the same data appear instead of just one.

[Jammin]

Here is an example of what I mean, attached is the input file (DEM_test) and the associated output file (DEM_testsubset). Each iteration is represented in the first column, instead of one entery there are multiple.

[Rodrigo_Cuenca]

Whats the purpose of the continue button?

Maybe you can try this, I remove the case structure, and move the continue button, it will stay in that loop until you press the button.

[Jammin]

The continue button is supposed to ensure the program waits until the user manually positions the cursors. The continue button is pressed once the cursors are in position, and the program proceeds to the next iteration. The button works fine, and the data that is output is correct, it is just that would like the vi to output one for for each iteration.

PS I have LV 8.6

[Rodrigo_Cuenca · Accepted solution]

Version 8.6

[Jammin]

Thanks Rodrigo. Just curious, most of the posts I have read seem to promote the use of event structures. Do you feel that they would be appropriate in this circumstance?

dave

[Rodrigo_Cuenca]

Yes, instead of polling the continue button, you can use an event structure, it should look something like this.