This is a suggestion to avoid having to do this with your macros:
This is time consuming, ineffective and just plain ugly. Instead, we could have a new action that sets the default pause between steps, so that we can avoid having to repeat the "Pause (0.7)" so many times.
The new action would look like this:
action 1 set default pause between actions to 0.7 (all following actions will have this pause in between)
....... set default pause between actions to 1.5 (now all following actions will have a 1.5s pause in between)
This new action has the scope of the current executing macro only, so that you don't accidentally mess up your macros.
What do you guys think? I hope you find this useful and support it to have it implemented.
Technically, you can already do this using the defaults write shell action and the private preference to define a pause between actions.
However, in my experience it is almost never the correct solution. Most actions have no need for a pause between them, and some actions require a very large pause between them, and if you have a uniform pause then it is likely to cause the macro to run much slower than necessary.
I may add something, but generally this is more an indication of a problem with the macro (or perhaps in this case really intractable applications).
Having the macro executing correctly, with fields properly validated is much more important than having it executed as fast as possible in this instance.
If this is already possible, could you please share the code as this is really really useful.
One thing I would find incredibly useful, would be a Record command option to automatically capture and insert delays (pauses) between commands. This would give me the option of getting something working instantly, that I could then go back, tweak and speed up, when I have time.
On the topic of pauses, has anyone else found that macros are executing a bit too fast in Yosemite? I have had to add short (~0.5 second) pauses after ‘Type Keystroke Tab’ to macros that ran perfectly prior to the Yosemite update. This happens to me in Mail, Direct Mail, and other applications. I am going to try the InterActionDelay setting since adding all those pause commands is a pain.
Thanks for the suggestion.