Meh! Like "NAP 1" in UniVerse on Windows is actually "NAP 18" - you can't actually NAP for 1 millisecond, the lowest resolution seems to be about 18 milliseconds.
YMMV Mike -----Original Message----- From: [email protected] On Behalf Of Dan McGrath Sent: Thursday, 8 April 2010 10:34 a.m. To: U2 Users List Subject: Re: [U2] UD: Phantoms Bill, I get similar results to your test program. INPUT PauseTime FOR I = 1 TO 10 StartTime = TIME() PAUSE PauseTime StopTime = TIME() CRT "Total time taken is " : OCONV(StopTime - StartTime, 'MTS'): CRT ", expected ": OCONV(PauseTime, 'MTS') NEXT I Run from ECL Input = 5, Times taken: 6,10,10,10,10,10... Input = 10, first time taken was 8, the next 9 where all 10. ... So, clearly PAUSE aligns itself to a 10 second boundary and can only operate on that. Given this, PAUSE works correctly for any 10 second increment, AFTER the first pause statement. Something like this should be added to the document, because according to the manuals 'PAUSE 5' should work, but in practice, it will actually running a 'PAUSE 10' with the first PAUSE statement pausing for an undefined period. Regards, Dan The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
