Skip to content

Commit f9e0afc

Browse files
committed
docs: clarify commbus api usage
1 parent 30322fa commit f9e0afc

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

DOCS.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Overview
22

3-
This document outlines the events used for communication with the WASM module. All data exchanged via these events is in the form of JSON strings. Remember to correctly stringify and parse this data for proper communication!
3+
This document outlines the events used for communication with the WASM module. All data exchanged via these events is in the form of JSON strings over the CommBus API. Remember to correctly stringify and parse this data for proper communication!
44

55
## Listener Events
66

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22

33
This is a barebones implementation to be able to download up-to-date Navigraph navdata into the sim (more specifically into the `work` folder of the aircraft).
44

5+
Documentation on the events used on the CommBus is located [here](/DOCS.md)
6+
57
## Repository Structure
68

79
Here's an overview on the structure of this repository, which is designed to be as simple as possible to use
@@ -27,7 +29,6 @@ Here's an overview on the structure of this repository, which is designed to be
2729
htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=navdata_interface.wasm&wasm_gauge=navdata_interface,0,0,1,1
2830
```
2931
- Note that if you already have a `VCockpit` with `NO_TEXTURE` you can just add another `htmlgauge` to it, while making sure to increase the index
30-
4. Everything is set! All you need to do now is make sure you provide the module with a proper download link. More on that [here](/DOCS.md)
3132

3233
## Building the Sample Aircraft
3334

0 commit comments

Comments
 (0)