![]() |
| |||||||
Workspace Macro Pro - Automation Edition Post messages and questions related to Macro Software for Windows Automation here. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Workspace Macro Pro In experimenting with writing my first macro, in edit mode, it seemed that the macro performed it sequence of steps much faster than the software I was applying the macro to could keep up with, and the macro failed. I got the bright idea of inserting a delay after the last successfully run macro step but found that the delay wasn't long enough. After numerous attempts at increaseing the delay time and running the macro many times, I finally got the macro to run past this step only to fail again to run completely at some later step. Can you please advise me on using a rule of thumb as to when to insert delays into your macros and for how long to set the delay? |
| |||
| Hello, In general, every application has its own response time and sometimes they are hard to find out with naked eye specially when they are in milliseconds. What I would recommend that works out in majority of the cases is, to record a macro in your application and then edit few minor things if required. If you use recorder then it will record the exact delays that you waited for during the recording and it will playback them accurately. So that way you do not have to worry about how much delay to wait for before every action while creating the task from editor. Hope that helps! |