# Example of Using Input Methods

> Example project comparing Hardware Events, Simulate, and Chromium API 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.

1. Open a Notepad window.
2. In Studio, from the **Basic Recording** toolbar, start the automatic recorder.
3. Type something into the Notepad window.
4. Minimize the window and restore it.
5. Type something else in the Notepad window.
6. Press Esc two times. The automation is saved and displayed in the **Designer** panel. It should look as in the following screenshot.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/activities/activities-docs-image-167003-df3ba413.webp)
7. Move the activity that restores the Notepad window after the second [Type Into](https://docs.uipath.com/activities/docs/type-into) one. We do this to check if the type of input method selected can also write to Notepad in background mode.
8. From the drop-down of the second **Type Into** activity, select **enter**. A special key string is displayed at the end of the previously-existing text.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/activities/activities-docs-image-166660-e54ab473.webp)
9. Copy the special key string at the beginning of the sentence. This enables you to test special keys, such as Enter that adds a new line in a text editor.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/activities/activities-docs-image-166704-df56edc3.webp)
10. Run the workflow once with every input method. Note the differences:

* The **Default** method – it does not automatically erase previously written text, supports special keys, but writing in the background does not work;
* The **SendWindowMessages**method – 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);

  ![docs image](https://dev-assets.cms.uipath.com/assets/images/activities/activities-docs-image-168269-ae72d9de.webp)
* The **Simulate Type/Click** method – works in the background, but it automatically erases pre-existing text, and does not support special keys.

  ![docs image](https://dev-assets.cms.uipath.com/assets/images/activities/activities-docs-image-167417-2032eaab.webp)

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.

[Download example](https://www.uipath.com/hubfs/Documentation/WorkflowExamples/Studio_v2019-fastTrack/UsingInputMethods.zip)