From d6af07989df23219293cf6117e6cd0ae6a63e2e9 Mon Sep 17 00:00:00 2001
From: Torbjörn Andersson
Date: Thu, 11 May 2006 08:25:09 +0000
Subject: This could be completely wrong, but I don't think
 Hotspot::stopWalking() is supposed to call setCurrentAction() in Resources,
 because then ScummVM will crash in getCurrentActionStr() whenever we try to
 interact with any object.

Since Hotspot::walkTo() calls setCurrentAction() in Hotspot, it seems like a
reasonable guess that this is the setCurrentAction() that stopWalking() should
call as well.

svn-id: r22409
---
 engines/lure/hotspots.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/engines/lure/hotspots.cpp b/engines/lure/hotspots.cpp
index b1501eff73..e4570148d6 100644
--- a/engines/lure/hotspots.cpp
+++ b/engines/lure/hotspots.cpp
@@ -308,7 +308,7 @@ void Hotspot::stopWalking() {
 	_actionCtr = 0;
 	_currentActions.clear();
 	Room::getReference().setCursorState(CS_NONE);
-	Resources::getReference().setCurrentAction(NONE);
+	setCurrentAction(NO_ACTION);
 }
 
 void Hotspot::setDirection(Direction dir) {
-- 
cgit v1.2.3