From 59cc43ccbbaf36214b855c835b6ada1470f078d0 Mon Sep 17 00:00:00 2001
From: Sam Lantinga <[EMAIL REDACTED]>
Date: Wed, 24 Apr 2024 09:38:26 -0700
Subject: [PATCH] Added a note about WIN+V for future reference (thanks
@orconut!)
---
src/video/windows/SDL_windowsevents.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/video/windows/SDL_windowsevents.c b/src/video/windows/SDL_windowsevents.c
index cb2a44c50b544..53af6be7114bb 100644
--- a/src/video/windows/SDL_windowsevents.c
+++ b/src/video/windows/SDL_windowsevents.c
@@ -318,7 +318,10 @@ static SDL_Scancode WindowsScanCodeToSDLScanCode(LPARAM lParam, WPARAM wParam)
* value set, however we cannot simply map these in VKeytoScancode() or we will be
* incorrectly handling the arrow keys on the number pad when NumLock is disabled
* (which also generate VK_LEFT, VK_RIGHT, etc in that scenario). Instead, we'll only
- * map them if none of the above special number pad mappings applied. */
+ * map them if none of the above special number pad mappings applied.
+ *
+ * WIN+V (clipboard history feature) can also send Ctrl-V without a scancode value set.
+ */
if (code == SDL_SCANCODE_UNKNOWN) {
code = VKeytoScancodeFallback(wParam);
}