Hovers the mouse over a specified UI element. Must be added inside an Application Card activity.
- Indicate Target - Indicate the UI element over which to hover by moving the mouse to it and clicking the element.
- After you indicate the target, click the Options button and then select one of the available options to further configure your target.
- Indicate Target - Indicate the target again.
- Configure Target - Configure advanced options for the target.
- Highlight Target - View the currently selected target on your display surrounded in a box.
- ContinueOnError - Specifies if the automation should continue even when the activity throws an error. This field only supports Boolean values (True, False). The default value is False. As a result, if the field is blank and an error is thrown, the execution of the project stops. If the value is set to True, the execution of the project continues regardless of any error.
- Delay After - Delay (in milliseconds) between the time this activity is completed and the time the next activity begins any operations. The default value is 300 milliseconds. Adding a delay between activities ensures that one activity has enough time to complete before the next activity begins.
- Delay Before - Delay (in milliseconds) between the time the previous activity is completed and the time this activity begins performing any operations. The default value is 200 milliseconds. Adding a delay between activities ensures that one activity has enough time to complete before the next activity begins.
- Display Name - The name displayed for the activity in the Designer panel. A display name is automatically generated when you indicate a target.
- Private - If selected, the data used by the activity is not saved to the StudioX logs when the project is executed.
- Input Mode - Select how to execute the hover:
- Same as Card - Use the same input mode as the Application Card. This is the default selection.
- Window Messages - Sends a specific message to the target application. This input method can work in the background, is compatible with most desktop apps, but it is not the fastest of the methods.
- Hardware Events - Simulates the hover by using the hardware driver. This is the slowest method, it cannot work in the background, but it is compatible with all desktop apps.
- Simulate - Simulates the hover using the technology of the target application. This input method is the fastest of the three and works in the background.
Updated 3 months ago