Collaboration diagram for Client API:
|
bb5/client directory.
More...Classes | |
| class | Api |
| User interface for graphical interface, AI, etc.
This class is really the "bridge" between the "coach" (whether it would be a human or a computer) and the rules engine. More... | |
| class | CBall |
| Ball for the client. More... | |
| class | CField |
| Field for the client. More... | |
| class | CPlayer |
| class | CPlayerMsg |
| Handle messages for CPlayer objects.
There is a single instance of this class, that dispatch message to the good CPlayer object. More... | |
| class | CRules |
| Rules implementation for the client. More... | |
| class | CTeam |
| Team implementation on client side. More... | |
| class | CTeamMsg |
| Handle messages for CTeam objects.
There is a single instance of this class, that dispatch message to the good CTeam object. More... | |
| class | Event |
| Base UI events class.
Derive from this class and virtual methods will be called... when time will come. More... | |
Enumerations | |
| enum | eSelTeam { TEAM1 = 0, TEAM2, US, THEM } |
| Constants for Api::selectTeam() parameter. More... | |
| enum | eCustomEvent { eInitGame } |
| Custom event identifier, for use as BaseCRules::onEvent(int) parameter. | |
bb5/client directory.
| enum eSelTeam |
Constants for Api::selectTeam() parameter.
1.4.7