Lot of questions !
Some answers :
a & b/ You should read the Help about the functions of the event structure. You will learn that it is used to react to specific events (mouse moves, value changes...). Here, I have used it to detect any change in the boolean array. That more efficient than being obliged to read periodically the array to see if something has been changed.
c/ I see that you tried to get the temperature values out of the loop. There are several mistakes there that demonstrate that you have not spent enough time/efforts with loops and arrays. Go through the examples shipped with LV, and read carefully the manuals. Basically, the temperatures should be compared with the reference temperature when they are read from the file, INSIDE the loop. As it is, you were trying to compare the values only after the stop button has been pressed...
Second mistake, in the index array function, you wired the line index, instead of the column index.
d/ Have you tried the button ? What is its effect ? How would you handle a situation where you have say 200 buttons ? Got it now ?
e/ the easiest way for the user to scroll through the data is probably to use the zoom tools provided by NI. Right-click the graph and make the graph palette visible. Then select the appropriate zoom tool. Of course, you may also play with the property nodes to fix the X scale. Just a comment : if you disable the autoscale property of the X scale, and if you change the axe min and max value, the scroll bar will appear. Is that something that you knew about ?
f/ no problem with the icons here.
g/ what do you mean by "looks odd" ? You could make the legend background transparent, to get something more conventional...
h/ what do you mean by "erratic" ?
In my applications, I usually store the time in several formats. In the first column, I usually put the date, then the time in the second column, then the time (seconds)elapsed since the beginning of the experiment, then the same info, but as decimal hours. If you can have only a single column for the time, use an unit which corresponds to the duration of your acquisition, decimal minutes, or decimal hours for instance. That will make data manipulation and display much easier.
CC
Chilly Charly (aka CC)