Class List

Here are the classes, structs, unions and interfaces with brief descriptions:

[detail level 123]

▶NDevices	Okay, the portable keyboard numbers don't work like the outside keypad because the outside keypad is numlock ON
CAnalog
▶CAnalogConfig
CChannel
▶CApcupsd	C++ monitoring implementation of http://www.apcupsd.org
CSTATUS
CApcupsdConfig
CApcupsdParam
CBass
▶CBassConfig
CSound
CDeviceList
CEncoder
CEncoderConfig
CInterfaceKit
▶CInterfaceKitConfig
CInput
COutput
CSensor
CJoystick
▶CJoystickConfig
CAxis
CButton
CKeyboard
▶CKeyboardConfig
CBuffer
CKey
CPrinter
CRakNet
CRakNetConfig
Csentence
CSpatial
▶CSpatialConfig
CAccelerationAxis
CTeamSpeak
CTeamSpeakConfig
CWebcam
CWebcamConfig
CXplane
CXplaneConfig
▶CYouTube
CPublishParameters
CYouTubeConfig
▶NLibrary
CMathUtils
CSolar
CStringUtils
▶NSystems	These have to be in this order
CBaseComponent
CBattery
CCombustion	Combustion Chamber is very specific, on or off set, we get the pulses
CComponent
CConnector
CDependency
CIgniter	Igniter is very specific, on or off set, we get the pulses
CN1	N1 is very specific, load differential
CN2	N2 is very specific, load differential
CReal	Real components simply take setState and apply it to currentState, they run their own fault states
CRelay
CStarter	Starter is very specific, load differential
CSwitch	Switch is a direct-set (no control voltage, command from bus from physical switch) which takes a supply and propogates it, no load
CTempSensor	Temperature sensor reads data from setState (or attached component?) and puts it on currentState assuming nothing is wrong with the sensor
CVirtualization
CAfcs	Automatic Flight Control System
CAlertMessageStack	Alert Message Stack (CAS)
CAltitudeTape	Altitude
▶CAse	Adaptive Scenario Engine
CSCommand
CSStep
CSVocalware
CSVoice
CAttitudeIndicator	AI
▶CBus
CAfcs	(25) Automatic Flight Control System (AFCS) modes and engagement status, including autothrottle;
CCas	Crew Alerting System
CCommand
CComponent
CCondition
CConfig
CDEVICE_OBJECT
CDiagnostics	Diagnostics
CDoor	CUSTOM## Door module
CElement
CFadec	Full Authority Digital Engine Control
▶CFcs	Flight Control System
CLocation
CFdr	Flight Data Recorder
CFlightModeAnnunciator	FMA
CFms	Flight Management System
CFont
CGpws	Forward definitions for the modules are below
CHeadingIndicator	Heading
CIndicatedAirSpeedTape	Forward definitions for the instruments are below
CInstrument	Abstract base class for instrumentation By definition, instruments don't do any of the work (they don't modify values) If you have something that takes data like VSI and AGL and then triggers GPWS that would be in a module This is presentation layer only - because we can have multiple copies of a particular instrument concurrently displayed What if we don't have data on the bus for the instrument, like FMS stores the waypoint order, waypoint locations? N1 and ITT are different, we are reading from sensors that could be flawed... not from FADEC directly
CITTIndicator	ITT
CLogger
CLogo	CUSTOM## Logo module
▶CMcu	Motion Control Unit
CSSnap
CMD5
CMessage
CModule	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
CMovingMap	MovingMap
CN1Indicator	N1
CNullable
CPage
▶CPfd	Primary Flight Display
CSLight
CRtu	Radio Tuning Unit
CSBasePacket
CSControlSurfaces	ID_USER_PACKET_ENUM + 0
CScreen
CSEvents	ID_USER_PACKET_ENUM + 3
CSFromDisplay	ID_USER_PACKET_ENUM + 2
CSInitialData	ID_USER_PACKET_ENUM + 1
CSPacketSetting
CSprite
CTcas	Traffic Collision Avoidance System
CText
CVehicle
▶CViewport
CADAPTER_OBJECT
CVmu	Voice Messaging Unit
▶CWatch
CCondition
CWaypoint
CWINDOW_OBJECT