12-31-2008 11:45 AM
12-31-2008 02:14 PM
Don't forget that whenever you have multiple instances of the same code, it might be easier to just use arrays instead.
Here's a very quick draft on how you could do things (LabVIEW 8.0). See if it is clear. 🙂
01-01-2009 12:38 PM
Is there a way to change the dialog string on the button itself? I would like to push the button to start acquiring data and have the button itself list acquiring data. Is it possible to click Go! and the button itself changes to Acquirring Data and then push it again and it changes to Waiting for Max Temp and then it changes when the max is reached and when pushed again the test is complete and the label goes back to "Start". There are 4 changes of state: Start, Gel, Peak, Stop. Data is collected between Start and Gel, Between Gel and Peak, and between Peak and Stop.
01-01-2009 12:47 PM
nicholas03 wrote:Is there a way to change the dialog string on the button itself?
No, because the button is part on an array. All elements of the array will have the same boolean text.
What you could do is make the buttons (incl. array container) transparent and place them on top of the string array, for example.
You could also use ring indicators (or disabled controls) instead of buttons. Do mouse-down events, calculate the element from the mouse coordinates and increment the ring array element accordingly.
There are many other ways to do all this. 🙂 Try some!
01-02-2009 10:33 PM - edited 01-02-2009 10:34 PM
01-02-2009 11:17 PM - edited 01-02-2009 11:18 PM
01-03-2009 02:13 AM
nicholas03 wrote:
I tried to send the vi as an attachment but was unable.
Use a different web browser or place the VI in a zip file before attaching.
Some browsers (safari, google chrome) cannot handle attachments with two-letter extensions (e.g. *.vi).
01-03-2009 05:37 PM
01-03-2009 08:28 PM - edited 01-03-2009 08:30 PM
(Ah sorry, I did not notice that my downconversion to 8.0 mutilated my nice "in-place" structure into a complicated one-iteration while loop. 😞 This is of course not needed!)
So anyway, things are thus way too complicated. Here's a very simple VI that just increments each TC state. Is that what you wanted?
(To absolutely eliminate any possibility of a race condition, I also use the new and old values from the event terminal)
01-04-2009 03:52 AM
altenbach a écrit: [...] (To absolutely eliminate any possibility of a race condition, I also use the new and old values from the event terminal [...]
Since you placed the Buttons control inside the event structure, do you think a possibility of race condition still exists (except if the "lock FP until the event complete" default behavior of the event frame was changed) ?