> For the complete documentation index, see [llms.txt](https://renkogurus.gitbook.io/renkogurus-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://renkogurus.gitbook.io/renkogurus-documentation/renkogurus-propbot-user-guide/vps-prop-bot/renkogurus-vps-dashoard/window-settings-panel.md).

# Window Settings Panel

<figure><img src="https://273289729-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXlGDI9rakMRwrwFoVorR%2Fuploads%2FY9EpyaQ7qAa6Rb8q7duz%2FScreen%20Shot%202025-05-04%20at%2010.37.23%20AM.png?alt=media&amp;token=c612a992-d34a-4b3b-846b-b92f130437a4" alt=""><figcaption></figcaption></figure>

#### 🖥️ Default Application

> ✅ **By default, the bot is configured to interact with** `Tradovate - Default Layout`\
> This is the most commonly used layout and works out-of-the-box for most users.

***

#### 🔍 Show Window Names

* Use the **“Show Window Names”** button to list all currently open windows.
* From the dropdown, **select the exact window name** that matches your trading app (e.g., `ThinkOrSwim`, `E*TRADE`, etc.).
* Then click **“Save Config”** to lock it in.

> 📌 This is essential when using **any application other than Tradovate**.

***

#### ⏱️ Delay Between Requests (ms)

* This defines the delay (in milliseconds) between simulated mouse/keyboard actions.
* **Use Case**:\
  If the default contract size in your platform is 1, but you want to simulate **multiple orders** (e.g., 2 or 3), then:
  * The bot will send multiple inputs.
  * Setting a small delay (e.g., `150ms`) allows the system to handle multiple requests without error.

***

#### 🧠 Window Identification Delay (ms)

* If the bot **fails to identify or focus the window** properly, increase this value slightly (e.g., to `250` or `300`).
* Useful in slower VPS environments or if multiple resource-heavy apps are running.

> 🔵 Normally, the default `150ms` is sufficient. Only adjust this if you face misclick or focus issues.

***

#### 🚨 Skip Window Identification (⚠️ Last Resort)

> ⚠️ **Use this only if nothing else works or you're experimenting with an unsupported application.**

* When checked, the bot will **skip automatic window identification completely**.
* You must:
  * **Manually click inside the trading application window** before running any commands.
  * **Keep your RDP session active and open** — **you cannot close or disconnect**, or the focus will be lost and automation will fail.

> 🚫 This disables all smart detection features and is not recommended for regular use.

***

#### ✅ Best Practices Summary

* ✔️ Use **Show Window Names → Save Config** when changing platforms.
* ✔️ Adjust **Delay Between Requests** for multi-order input.
* ✔️ Only change **Window Identification Delay** if there are targeting issues.
* ❗ Use **Skip Window Identification** only if all else fails — and never disconnect RDP in this mode.