From 9080c696bb9fbf12447403a95a5cbb8428e60b55 Mon Sep 17 00:00:00 2001
From: bicarus <202771338+bicarus-dev@users.noreply.github.com>
Date: Tue, 21 Jul 2026 15:39:45 -0700
Subject: [PATCH] Updated Configuring touch screens as subscreen (markdown)

---
 Configuring-touch-screens-as-subscreen.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Configuring-touch-screens-as-subscreen.md b/Configuring-touch-screens-as-subscreen.md
index 75d0dea..40ca52c 100644
--- a/Configuring-touch-screens-as-subscreen.md
+++ b/Configuring-touch-screens-as-subscreen.md
@@ -48,6 +48,8 @@ It's helpful to understand that Windows doesn't know if your second display has
 
 ## Step by step instructions
 
+### For full screen
+
 1. Connect your touch screen (usually, HDMI for display, USB for touch input, and power)
 1. Make sure it can display things, and touching on the screen results in input. Confirm by dragging around on the Windows desktop. You probably see the selection lasso on the touch screen, right underneath your fingers.
 1. In Windows display settings, ensure that your main monitor is set to primary - **not** the touch screen.
@@ -57,6 +59,10 @@ It's helpful to understand that Windows doesn't know if your second display has
 1. Follow instructions on the screen. "Lie" so that Windows thinks the primary screen is a touch screen.
 1. To confirm that things were set up correctly, try touching again. The selection lasso should now appear on your primary screen.
 
+### For windowed mode
+
+Do the same as above, but don't "lie" this time, let Windows know that your touch screen is where the touches must be routed.
+
 ## Troubleshooting
 
 Touch monitors are finicky things, and a lot of the times, devices do not properly implement the correct touch API needed, resulting in missed touches, duplicated touches, inability to use multi-touch, not recognizing taps, not recognizing swipes, etc. It's the wild wild west out there, but Spice has a few options to deal with them.