From 3059c95abd3944e6e628a32238dca1aeefecadbc Mon Sep 17 00:00:00 2001
From: Tobia Tesan
Date: Wed, 21 Jun 2017 10:51:06 +0200
Subject: DIRECTOR: Handle keyDown in 1-ary processEvent

Might change semantics by calling the standard chain for input events.

That is what the D4 docs suggest anyway.
---
 engines/director/events.cpp             | 2 +-
 engines/director/lingo/lingo-events.cpp | 4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/engines/director/events.cpp b/engines/director/events.cpp
index 81c80dcc1e..b59202c1f6 100644
--- a/engines/director/events.cpp
+++ b/engines/director/events.cpp
@@ -110,7 +110,7 @@ void DirectorEngine::processEvents() {
 					warning("Keycode: %d", _keyCode);
 				}
 
-				_lingo->processEvent(kEventKeyDown, kGlobalScript, 0);
+				_lingo->processEvent(kEventKeyDown);
 				break;
 
 			default:
diff --git a/engines/director/lingo/lingo-events.cpp b/engines/director/lingo/lingo-events.cpp
index e1a8cab7ba..15595b53ee 100644
--- a/engines/director/lingo/lingo-events.cpp
+++ b/engines/director/lingo/lingo-events.cpp
@@ -175,6 +175,10 @@ void Lingo::processInputEvent(LEvent event) {
 			else
 				g_lingo->processEvent(kEventNone, kFrameScript, currentFrame->_sprites[spriteId]->_scriptId);
 		}
+		if (event == kEventKeyDown) {
+			// TODO: is the above condition necessary or useful?
+			g_lingo->processEvent(event, kGlobalScript, 0);
+		}
 		runMovieScript(event);
 	}
 }
-- 
cgit v1.2.3