|
inputClasses
Input variants implemented by classes
Phase-Requirements IntroductionSome basic input styles. Implement the wished class, configure it if necessary, and get full input interaction. DetailsConsist of following classes:
Code Filescinput.h - base class ci3rd.h cirts.h ciarcade.h cirpg.h Code design concernsGeneral questionsMenu and GUI Interaction belongs to the base class (if really needed there) Variation 1 : Data exchangeModels to interact with should be attachble to the input object, events handled by callbacks. That would raise dependencies from the game object classes and but would handle all input centralized in the input derivates. On the other hand, the object could simply store state variables, which represents the latest input, so the game can react on these values given by the input. Here you have the freedom to react on input whereever, whenever, however depending on the interface. At cost of a clear overview, where what happens. |