Displaying a timed message in test panel for 10 seconds

Question

What is the best way to display a timed  pop-up message in the current test panel?
Solved!
Go to Solution.

Answer 1

OMHG^ (oh my holy god above)
I'll post a decent wait routine from work tomorrow.  
NI  --- will you buy, or rent, an horologist?
jc-
do you know what KIND of "time" you are "waiting"  Again, "Time" is
measured in SI seconds and equal to a specific number of transisitions
between two hyperfine states of the valence electron on a specific
isotope of a Cesium atom.  NIST submitts their approximation of "Time"
to an international body for correction on a (ir)regular basis
"Civil Time" (local day-time) is a legal,
not measurably traceable, term and is coordinated globaly.  "Civil
Time" as a legal term and has no scientific measurement related to
"Time."
Assuming (big assumption) that you care nothing
about "Civil Time" (time of day) nor "Time" (a root dimension), an OS
system mS timer has a value that is useful for these types of
applications. 
LabVIEW has two independant type
definitions "Time Stamp", a cluster derivitive from local "Civil Time"
represented by the OS System clock (the calaibration is left to the OS)
and "mStimer.value", derived directly from the OS mStimer dependant
only on OS procesess (the calaibration is non-existant)
That
being said,  the mS timer of a PC is a U32 int.  Add U32 int + unk
(coerced to an XXInt) and the result may be greater than the largest
possible "mStimer.value".  once every so many weeks the mStimer rolls
over----- Now if you are "Waiting" for mStimer.value to be greater than
+inf..........(that could take forever)  Smile everybody its
happened to me! and the reason I became an amature horologist (plz
don't tell my wife- she's still waiting)
Of course,
simple math can predict an overflow of a U32.  I do it all
the "Time" with the Delay vi I wrote to avoid waiting
forever.
Who else has written one? 
  is NI stuck in this same loop with the fix for Wait +(mS).vi?