Execution starts in main() (main.c of DROD project). After some initialization is performed the screen manager is called to activate a screen. Each screen has its own set of event notification methods that are called while it is active. The code for receiving events and call event notifiers is in CEventHandlerWidget, but if you understand the events, it isn't really necessary to delve deeply into event-handling code. Events are mostly self-explanatory, mouse clicks, key presses, etc. See comments in eventhandlerwidget.h about specific events.
The screens also contain widgets. Widgets are things like list boxes, buttons, scroll bars, and other UI elements. The display of the DROD room is also encapsulated inside of a CRoomWidget.
Player commands are received via CGameScreen :: OnKeyDown() and sent to an instance of CCurrentGame. CRoomWidget gets information about the room from CCurrentGame and draws the room. This is just the user interface of the game. The game logic itself is all contained in CCurrentGame, with a very clean division from UI code. You won't find any code in CCurrentGame to update the screen or play sounds. CCurrentGame only concerns itself with updating the logical representation of the room in response to player commands. Because CCurrentGame cannot handle UI tasks, it passes a CCueEventList with descriptions of events that occured. The UI code decides if it needs to show a blood splatter animation, play the level complete sample, or whatever.
That's an overview. Ask about anything else you'd like to know.
-Erik
____________________________
The Godkiller - Chapter 1 available now on Steam. It's a DROD-like puzzle adventure game.
dev journals |
twitch stream |
youtube archive (NSFW)
