| ▼NWASimCommander | WASimCommander main namespace. Defines constants and structs used in Client-Server interactions. Many of these are needed for effective use of WASimClient, and all would be useful for custom client implementations |
| ▼NCLI | WASimCommander::CLI namespace. Container for implementation of the C++ WASimCommander API and WASimClient as a C++/CLI .NET "wrapper." The primary documentation is for the C++ version equivalents. Documentation for everything in the CLI namespace focuses primarily on any (non-obvious) differences from the C++ version |
| ▼NClient | WASimCommander::CLI::Client namespace. Implementation of the C++ WASimClient as a C++/CLI .NET "wrapper." |
| CWASimClient | C+/CLI wrapper implementation of WASimCommander::Client::WASimClient. See documentation for the C++ class for most of the details. Only implementation differences are documented here |
| ▼NStructs | WASimCommander::CLI::Structs namespace. CLI/.NET versions of WASimCommander API and Client data structures |
| CClientEvent | Client Event data, delivered via callback |
| CCommand | Command data structure. The member contents depend on the command type as described in each command type of the CommandId enum documentation |
| CDataRequest | Structure for value update subscription requests |
| CDataRequestRecord | DataRequestRecord inherits and extends WASimCommander::CLI::Structs::DataRequest with data pertinent for use by a data consumer/Client. In particular, any value data sent from the server is stored here as a byte array in the data member (a byte array) |
| CListResult | Structure for delivering list results, eg. of local variables sent from Server |
| CLogRecord | Log record structure |
| CRegisteredEvent | Structure to hold data for registered (reusable) calculator events. Used to submit events with WASimClient::registerEvent() |
| CVariableRequest | Structure for using with WASimClient::getVariable() and WASimClient::setVariable() to specify information about the variable to set or get. Variables and Units can be specified by name or by numeric ID |
| CValueTypes | Predefined value types |
| ▼NClient | WASimCommander::Client namespace. Defines/declares everything needed to interact with the WASimCommander Client API, including the WASimClient class itself |
| CClientEvent | Client Event data, delivered via callback |
| CDataRequestRecord | DataRequestRecord inherits and extends WASimCommander::DataRequest with data pertinent for use by a data consumer/Client. In particular, any value data sent from the server is stored here as a byte array in the data member (a std::vector of unsigned char) |
| CListResult | Structure for delivering list results, eg. of local variables sent from Server |
| CRegisteredEvent | Structure to hold data for registered (reusable) calculator events. Used to submit events with WASimClient::registerEvent() |
| CVariableRequest | Structure for using with WASimClient::getVariable() and WASimClient::setVariable() to specify information about the variable to set or get. Variables and Units can be specified by name or by numeric ID. Only some variable types have an associated numeric ID ('A', 'L', 'T' types) and only some variable types accept a Unit specifier ('A', 'C', 'E', 'L' types). Using numeric IDs, if already known, is more efficient on the server side since it saves the lookup step |
| CWASimClient | WASimCommander Client implementation. Handles all aspects of communication with the WASimCommander Server WASM module |
| CCommand | Command data structure. The member contents depend on the command type as described in each command type of the Enums::CommandId enum documentation |
| CDataRequest | Structure for variable value subscription requests |
| CKeyEvent | Data structure for sending Key Events to the sim with up to 5 event values. Events are specified using numeric MSFS Event IDs (names can be resolved to IDs via Lookup command). This supports the new functionality in MSFS SU10 with trigger_key_event_EX1() Gauge API function (similar to SimConnect_TransmitClientEvent_EX1()). The server will respond with an Ack/Nak for a SendKey command, echoing the given token. For events with zero or one value, the SendKey command can be used instead |
| CLogRecord | Log record structure |
1.12.0