On OS X, you can use ‘the long seconds’. On Windows and with a commercial LiveCode, you might be able to use darzTimer plugin to help with measuring looping delays.
I haven’t looked at that in years. Find it here: http://pages.swcp.com/dsc/revstacks.html It is a plugin stack with an embedded external. Unfortunately, it is locked and I will have to go and unzip some files in some old CDs to find an unlocked version. Another approach for Windows is to calibrate your delay command by calling it a thousand times at the start. You might even thousand, tweak, thousand, tweak. It might cost a half second at a slash screen, though. That should work for OS X, too. Dar Scott Externals and Libraries On May 28, 2014, at 9:37 AM, Rick Harrison <harri...@all-auctions.com> wrote: > Hi there, > > I’m trying to speed up my application by reducing my wait times. > > Unfortunately, the wait command itself says that the minimum > wait time is 1 millisecond. > > I want to reduce my wait times to .5 or .25 milliseconds. > > I’m thinking perhaps a loop to wait just a few cpu cycles. > > It would be best if I could start and stop a timer which would > tell me exactly how much time has passed executing my loop. > > Ideas? Suggestions? > > Thanks, > > Rick > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
