mirror of
https://github.com/vcmi/vcmi.git
synced 2024-12-24 22:14:36 +02:00
9bfe000724
Currently closing game while network thread is waiting for something is very bug-prone, since network thread may resume during shutdown and access partially destroyed client state. Now if exit has been requested, the very first step would be semi- graceful shutdown of network thread (via exception throwing). This may in theory skip some cleanup in non-RAII code, but since game is shutting down this does not matters much. This logic applies to: - shutting down while network thread is waiting for dialogs - shuttind down while network thread waiting for animations in combat |
||
---|---|---|
.. | ||
Goals | ||
Pathfinding | ||
AIhelper.cpp | ||
AIhelper.h | ||
AIUtility.cpp | ||
AIUtility.h | ||
ArmyManager.cpp | ||
ArmyManager.h | ||
BuildingManager.cpp | ||
BuildingManager.h | ||
CMakeLists.txt | ||
FuzzyEngines.cpp | ||
FuzzyEngines.h | ||
FuzzyHelper.cpp | ||
FuzzyHelper.h | ||
main.cpp | ||
MapObjectsEvaluator.cpp | ||
MapObjectsEvaluator.h | ||
ResourceManager.cpp | ||
ResourceManager.h | ||
StdInc.cpp | ||
StdInc.h | ||
VCAI.cbp | ||
VCAI.cpp | ||
VCAI.h | ||
VCAI.vcxproj | ||
VCAI.vcxproj.filters |