09-27-2015, 06:35 AM
1. A human and an automation program cannot simultaneously use keyboard/mouse on the same computer, unless the macro runs on a virtual PC like Virtual Box or Vmware Player. If the macro fails on Virtual Box, it would probably fail on host computer too; need to change something in the macro.
There are functions that can automate background windows without using keyboard/mouse. Look in floating toolbar -> Window/control -> Accessible object. Not so easy to use.
2. Use a window trigger.
3. To make macro continue on error, insert this at the beginning:
opt err 1
But in most cases the macro then will do bad things on error. Use the 'opt err 1' carefully.
To avoid errors caused by a too short wait time, use 'wait for' functions, for example 'wait for window', with bigger timeout.
Currently there are no better choices. Future Quick Macros versions should have an option like this: on error pause macro and ask the user what to do (wait more etc), maybe even to edit&continue macro without ending it.
There are functions that can automate background windows without using keyboard/mouse. Look in floating toolbar -> Window/control -> Accessible object. Not so easy to use.
2. Use a window trigger.
3. To make macro continue on error, insert this at the beginning:
opt err 1
But in most cases the macro then will do bad things on error. Use the 'opt err 1' carefully.
To avoid errors caused by a too short wait time, use 'wait for' functions, for example 'wait for window', with bigger timeout.
Currently there are no better choices. Future Quick Macros versions should have an option like this: on error pause macro and ask the user what to do (wait more etc), maybe even to edit&continue macro without ending it.