Abstract base class for modules By definition, instruments don't do any of the work (they don't modify bus values) If you have something that takes data like VSI and AGL and then triggers GPWS that would be in a module It is a computer but not on the component level, it only has access to bus values from other modules.
More...
#include <Module.h>
Abstract base class for modules By definition, instruments don't do any of the work (they don't modify bus values) If you have something that takes data like VSI and AGL and then triggers GPWS that would be in a module It is a computer but not on the component level, it only has access to bus values from other modules.
Definition at line 11 of file Module.h.
◆ Module() [1/2]
◆ Module() [2/2]
Module::Module |
( |
Bus * |
prmBus | ) |
|
|
inline |
◆ ~Module()
virtual Module::~Module |
( |
| ) |
|
|
inlinevirtual |
Polymorphism gotcha - if this isn't here then std::vector embedded in derived classes don't clean up!
- See also
- http://www.cplusplus.com/forum/general/17754/ My theory is that they won't inherit a public destructor if one isn't declared in the base class
Definition at line 30 of file Module.h.
◆ FrameMove()
virtual void Module::FrameMove |
( |
float |
fElapsedTime | ) |
|
|
pure virtual |
Implemented in Logo, Door, Fdr, Fms, Ase, Afcs, Pfd, Mcu, Rtu, Cas, Fadec, Fcs, Vmu, Tcas, and Gpws.
◆ bus
The documentation for this class was generated from the following file: