>The program below shows the proper syntax, allowing 68K, PPC or FAT.
>
>Note that the components of the microSecRecord are defined as the new FB^3
>type UNSIGNED LONG. The definition unfortunately reveals a bug in release 0
>of FB^3: it cannot print variables of that type.
>
>You can print them with the help of the STR$ function, but _another_ bug is
>revealed: the UNSIGNED nature is lost. Since microSecLo counts MOD
>4294967296, it has a period of 4294.967296s (about 71 minutes).
>STR$(myMS.microSecLo) therefore displays as a positive number for 35
>minutes then negative for 35 minutes. The UNS$ function correctly displays
>myMS.microSecLo as always positive, but it shouldn't be necessary to use
>UNS$ on an already UNSIGNED variable.


Robert:

Do you have a function that will delay a program in milliseconds? Something
like:

LOCAL FN delayMS(theDelay)
  DIM i

   FOR i = 1 TO theDelay
      'do something to cause a one ms delay
   NEXT
END FN

tedd

PS: Please note that the above function would not use ON TIMER -- which is
something I don't normally use anyway. In fact, I don't see any reason for
using ON TIMER other than to complicate one's program flow.

PSS: Also note that the above function should also accommodate different
speed computers. In other words, it should have a standardized initial
testing function to set the delay.

___________________________________________________________________
<mailto:tedd@...>	               http://sperling.com/