ui.backend.windows: ToUnicode can return 0 and it's not an error that

should crash Factor.

You can trigger this by spamming alt-shift-k in the Windows ui with a
korean keyboard selected.

diff --git a/basis/ui/backend/windows/windows.factor b/basis/ui/backend/windows/windows.factor
index 0982ae37704214c4a54d6d9636725edfe6d7009f..0cc51099cd21e0a6fb15a7da224c83e96f054c7f 100644 (file)
--- a/basis/ui/backend/windows/windows.factor
+++ b/basis/ui/backend/windows/windows.factor
@@ -336,7 +336,7 @@ CONSTANT: exclude-keys-wm-char
             lParam -16 shift 0xff bitand :> scan-code
             keyboard-state GetKeyboardState win32-error=0/f
             VK_CONTROL VK_CAPITAL [ 0 swap keyboard-state set-nth ] bi@
-            wParam scan-code keyboard-state chars 2 0 ToUnicode dup win32-error=0/f
+            wParam scan-code keyboard-state chars 2 0 ToUnicode
             1 <=  [
                 1 chars nth 8 shift 0 chars nth bitor
             ] [