Jim You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7
Though I don't have it installed at the moment, the traditional DAQ palette (counter, I believe) has had the wait with error in/out function for many years.
I did myself one subVI, just like the MarcoMauri idea. Adding error terminal to the standard function will not hurt anyone and will be back compatible with existing code, so kudos!
For completeness, would you expect an error cluster on "Wait Until Next ms Multiple", "Tick Count (ms)", and "Get Date/Time in Seconds"?
My mind is blank right now, but can anyone list any functions that are guaranteed not to generate an error yet use an error cluster (in order to allow data flow enforcement)? ("Clear Errors" doesn't count!)
I sized mine to one terminal height since the error in and out are the only flow terminals required. The "mSec to wait" and "cancel wait" is sectioned in the bottom middle. This allows other terminals to flow from the previous VI to the next VI without having to go around the Wait VI.
I have wanted this implemented for a long time. Sequence structures are frowned upon but sometimes you need to wait a bit after you do something. To accomplesh this 'dataflow enforcement' i have even made a subvi that looks like this inside:
Somehow creating this subvi always feels necessary and pointless at the same time, like some logical conundrum. lol.
I love the openG vi's but I always fear someone would come along and try to use my code that hasn't installed the openG functions and my VIs would be broken with a mystery "?" stuck in important places 🙂
Kudos to this idea 🙂
--------------------------------- [will work for kudos]
