mirror of
https://github.com/vcmi/vcmi.git
synced 2024-11-30 08:57:00 +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 |
||
|---|---|---|
| .. | ||
| CGuiHandler.cpp | ||
| CGuiHandler.h | ||
| CIntObject.cpp | ||
| CIntObject.h | ||
| CursorHandler.cpp | ||
| CursorHandler.h | ||
| EventDispatcher.cpp | ||
| EventDispatcher.h | ||
| EventsReceiver.cpp | ||
| EventsReceiver.h | ||
| FramerateManager.cpp | ||
| FramerateManager.h | ||
| InterfaceObjectConfigurable.cpp | ||
| InterfaceObjectConfigurable.h | ||
| MouseButton.h | ||
| Shortcut.h | ||
| ShortcutHandler.cpp | ||
| ShortcutHandler.h | ||
| TextAlignment.h | ||
| WindowHandler.cpp | ||
| WindowHandler.h | ||