Input actions and methods
Automation requires certain properties to be configured to work seamlessly during the execution of the process. To perform either foreground or background automation, the input needs to be actioned in a GUI either directly by the user or by the robot. There are three types of input methods, which we will discuss now.
Default or hardware events
The default application mimics a mouse event or keyboard event using the hardware driver to communicate with the GUI. This is selected when SendWindowMessages and SimulateType are disabled by default, as shown in Figure 10.51. In the case of this event, the robot exactly mimics human actions, such as moving the cursor and clicking on a UI element. The UI elements need to be visible for this event to be successful.
Figure 10.51 – Default method
The key characteristics of the default method are as follows:
- It is 100% compatible with all applications.
- It runs only in the...
