Topics: Recorder, Command, Big Data, Comm Tech
In the main application window, the most critical button that its name is starting to record. Do some recording and hit the button. After that, move the mouse and do some clicks and when it is done, just hit stop or press central Q and go back to the main window. In this case, the macro recorder has created a script for the user, which consists of nothing but delays in mouse moves. It says wait for 499 milliseconds. Then move the mouse to 108 seventy-four screen coordinates. Then wait a bit more, then move the mouse again, and so forth. Play with it and see how it works. The mouse works all by itself, and when the playback is finished, hit play again or hit close to go back to the main window. After that, delete everything for now and create a macro instead of the recorder working on it. There is a need for a macro recorder to start Windows Notepad. Then, insert a launch file command and type it in notepad. Then, there is a need for a macro to wait until the notepad is launched. For example, adding the delay, 200 milliseconds will be just fine, or which is more convenient. A wait-for-process has been added that will wait for the notepad to start instead of just adding a random delay. A script has been created that starts notepad and then remains until the notepad is begun. Because it’s Windows, users never know if it is activated or not. With a macro recorder, type some text into the notepad window. Furthermore, add a type text command to the macro, for example: “hi there, notepad.” Play this macro and see how it works. The notepad has started, and there the text is in it. Users can play it again and again. There is a coping trophy instead of clicking plug and play again—opening notepad sides with lots of notepad phrases.