LabVIEW
Program unresponsive after a dialog box input
When it comes to state machines, shift registers are your friends. You can pass to the next state what the timeout should be. You can also pass what state to go to when there is a timeout. A timeout of -1 is a wait forever.
@bronsonmock wrote:
@billko wrote:What you probably didn't read was LabVIEW help for event structures, "caveats and recommendations for using events."
Thanks, That one was helpful. I think that article is pointing to what Crossrulz is hinting at.
<snip>
Don't worry - you just fell into one of the classic rookie mistakes - not knowing how helpful the help file really is. In fact, one of the BEST ways of learning LabVIEW is by enabling context help - the [?] in the upper-right corner of both the BD and the FP - and mousing over the thing that you have questions about. If that doesn't help, many times there is a "detailed help" link in the context help that takes you to the help for that item. 🙂
