From e3be574936e742656904847c551c946eb1d8f314 Mon Sep 17 00:00:00 2001
From: Torbjörn Andersson
Date: Mon, 31 Aug 2015 07:08:20 +0200
Subject: SHERLOCK: Add missing events.getKey() when checking for "pending D
 keys"

This is consistent with what happens when checking for "pending U
keys", so I think it's correct, but the Scalpel keyboard handling
doesn't work very well at the moment anyway. Probably at least partly
because of the way it mixes char and Common::KeyCode. I haven't
been able to wrap my head around it...
---
 engines/sherlock/scalpel/scalpel_user_interface.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'engines')

diff --git a/engines/sherlock/scalpel/scalpel_user_interface.cpp b/engines/sherlock/scalpel/scalpel_user_interface.cpp
index a67d464a11..efcf6ea05b 100644
--- a/engines/sherlock/scalpel/scalpel_user_interface.cpp
+++ b/engines/sherlock/scalpel/scalpel_user_interface.cpp
@@ -860,7 +860,7 @@ void ScalpelUserInterface::doEnvControl() {
 				// Check whether there are more pending D keys pressed
 				moreKeys = false;
 				if (events.kbHit()) {
-					Common::KeyState keyState;
+					Common::KeyState keyState = events.getKey();
 					_key = toupper(keyState.keycode);
 
 					moreKeys = _key == 'D';
-- 
cgit v1.2.3