Refactor: BusyMode class in libdoomsday, BusyRunner for the client
BusyMode handles the basic mechanics of busy mode. It optionally hands the tasks over to a ITaskRunner object, which in the client's case starts the worker callback in a background thread.
DoomsdayApp owns the BusyMode instance, while ClientApp owns the BusyRunner instance. The server uses the default BusyMode behavior.
The Busy API became almost fully obsolete: only the game freezing function remains. Other functionality is available directly via libdoomsday.
Added by skyjake about 9 years ago
Added by skyjake about 9 years ago
Refactor: BusyMode class in libdoomsday, BusyRunner for the client
BusyMode handles the basic mechanics of busy mode. It optionally hands
the tasks over to a ITaskRunner object, which in the client's case
starts the worker callback in a background thread.
DoomsdayApp owns the BusyMode instance, while ClientApp owns the
BusyRunner instance. The server uses the default BusyMode behavior.
The Busy API became almost fully obsolete: only the game freezing
function remains. Other functionality is available directly via
libdoomsday.