aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTorbjörn Andersson2015-08-31 07:08:20 +0200
committerTorbjörn Andersson2015-08-31 07:10:49 +0200
commite3be574936e742656904847c551c946eb1d8f314 (patch)
tree7990710506ca8217261a298ec57d84a701ac570a
parentc8a7e39e0522b32e29ab403188f56bee9cf1da27 (diff)
downloadscummvm-rg350-e3be574936e742656904847c551c946eb1d8f314.tar.gz
scummvm-rg350-e3be574936e742656904847c551c946eb1d8f314.tar.bz2
scummvm-rg350-e3be574936e742656904847c551c946eb1d8f314.zip
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...
-rw-r--r--engines/sherlock/scalpel/scalpel_user_interface.cpp2
1 files changed, 1 insertions, 1 deletions
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';