Why do we need UI actions?
Over time, countless applications for Windows were created, of which a great many still exist to this day. Microsoft itself has created excellent options for tailoring your applications with tools such as Visual Basic and Visual Studio. However, many of these applications are still not accessible via an API and have to be operated manually – also known as the human interface.
As we will see later in this book, PAD can work directly with numerous and widely used standard applications such as Office and Outlook, but it would be impossible to cover the wealth of different applications with dedicated actions. And that is the reason why the actions for UI elements exist. The term UI automation refers to the general capability of PAD to work with any application window and therefore remote control any application and control element.
To enforce this very general approach, the actions in this action group are correspondingly general and can be divided...
