Use this function to add Delay timing to macros. Delays may be necessary to allow time for a window to gain focus before the macro can proceed correctly or for any number of other reasons. The delay helps ensure that the macro doesn't play back faster than Windows can keep pace.



Script Editor >  Expand Timing Category > Delays



Timed delay in seconds / Timed delay in milliseconds

The Timed Delay in Seconds option puts Macro Express into a "wait state" where virtually no CPU cycles are used, thus allowing CPU intensive programs to continue uninhibited. This is similar to the Wait for Time to Elapse command. Select either the Timed delay in seconds or Timed delay in milliseconds option and then enter the number of seconds or milliseconds in the Delay Time edit box.



Note: This command suspends Macro Express for the amount of time specified. During this time the macro cannot be terminated by pressing the Scroll Lock + Pause keys or by right clicking on the "Running Man" icon in the notification area.



Delay in seconds / Delay in milliseconds

Delays can be set in seconds (up to 99999 seconds allowed) or in milliseconds (thousandths of a second). Just click on the option preferred and enter the number of seconds or milliseconds in the Delay Time edit box. Seconds can be in fractions of a second by using a decimal point such as .5 to signify a half second delay. Or 350 milliseconds equates to a little over 1/3 of a second delay.





Ignore Macro Speed Factor

This option instructs the Delay command to ignore the Macro Playback Speed so that the delay time remains constant. If this option were not checked and a Macro Speed command instructs the macro to play back at four times its normal speed, the delay would also be sped up. For example a one second delay would be reduced to a one quarter second delay.



Note: Delay timing halts the macro for at least the amount of time specified. The delay works by continually checking to see if the specified time has elapsed. While checking, any waiting or new Windows commands are processed. If a Windows command that takes a bit of time happens to be processed, then the delay may last longer than the time specified.