RenkoGurus
  • Getting Started
    • What is TradingView?
    • How to setup RenkoGurus Indicators
    • How to get updates
    • How to setup alerts in TradingView
  • Indicators
    • RenkoGurus-Consolidation & Breakout Filter
      • Signals
      • Settings
      • Alerts
    • RenkoGurus-SmartTrend
      • Signals
      • Settings
      • Alerts
    • RenkoGurus-SmartChannel
      • Signals
      • Settings
      • Alerts
    • RenkoGurus-SmartMoney
      • Signals
      • Settings
      • Alerts
    • RenkoGurus-PowerMeter
      • Signals
      • Settings
      • Alerts
  • RenkoGurus-PropBot-User-Guide
    • Onboarding
    • Non VPS Prop Bot
      • Tradovate/NinjaTrader Prop Bot
        • APIs & Payloads
      • TopstepX PropBot
        • APIs & Payloads
    • VPS Prop Bot
      • RenkoGurus VPS Dashoard
        • Bot Status Panel
        • Customer Info Panel
        • Actions Panel
        • Trade Command Panel
        • Window Settings Panel
        • Trading Hours Settings (GMT) Panel
        • Alerts Configuration Panel
      • RenkoGurus VPS Metrics Dashboard
Powered by GitBook
On this page
  1. RenkoGurus-PropBot-User-Guide
  2. VPS Prop Bot
  3. RenkoGurus VPS Dashoard

Window Settings Panel

PreviousTrade Command PanelNextTrading Hours Settings (GMT) Panel

Last updated 17 days ago

🖥️ 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.