From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
04-02-2010 09:59 AM
I want to disable the button when the user presses it, and if a previous button was on, then turn it off and enable it.
I can't quite see where am I going wrong.
Thanks
Kas
Solved! Go to Solution.
04-02-2010 10:03 AM
Well, for one thing, having an event structure inside one of the cases of a state machine is a bad idea. Methinks you may want to look at the producer-consumer architecture.
As for the actual code: Can't guess - the subVI that does the work is not included.
04-02-2010 10:18 AM
Uh, sorry, forgot to include the subvi.
P.S. Why would an event inside a case structure be bad? I would've thought this is common for state machine programming.
Thanks
Kas
04-02-2010 10:47 AM
The way you have it right now your event structure locks up your state machine. I don't know where you're going with the program, but one could argue that your state machine is not necessary.
As for other issues:
04-02-2010 03:18 PM
hah now there's a thought. I never thought I can modify radio buttons in that manner.
Thanks
P.S. Congradulations on becoming a Night. Well deserved.
Thanks
Kas