- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Example of Using Input Methods
To get a clearer picture of how these three methods work, let’s create a simple project that writes something in a Notepad window and switch between the three input methods.
- The Default method – it does not automatically erase previously written text, supports special keys, but writing in the background does not work;
-
The SendWindowMessagesmethod – works in the background, supports special keys, but it does not erase pre-existing text (you have to manually select the Empty Field check box in the Properties panel);
-
The Simulate Type/Click method – works in the background, but it automatically erases pre-existing text, and does not support special keys.
Therefore, be careful to choose the method that best suits your needs. If special keys are a must, you might want to avoid the Simulate Type/Click method, or if speed is what matters most, then maybe Simulate Type/Click is the right one.