From dcb3510bd8bc346e4e8c7ceb7f01f4e3d32f78ee Mon Sep 17 00:00:00 2001 From: ganicke Date: Mon, 11 Sep 2017 16:31:55 -0700 Subject: [PATCH] Include links to message bus souces in the DAL. --- docs/device/mes-events.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/device/mes-events.md b/docs/device/mes-events.md index 00d6d9e9..b669fa78 100644 --- a/docs/device/mes-events.md +++ b/docs/device/mes-events.md @@ -4,6 +4,21 @@ Events and event values are generated in the Message Event Service (MES). Using The event source IDs represent a device feature category. The event values are actions for, or notifications about a device feature. +### ~hint + +**MES system sources** + +The MES events are defined in this source file of the **[microbit-dal](https://github.com/lancaster-university/microbit-dal)**: + +* [MESEvents.h](https://github.com/lancaster-university/microbit-dal/blob/master/inc/bluetooth/MESEvents.h) + +Also, you can see how the message bus works in the DAL core files: + +* [MemberFunctionCallback.cpp](https://github.com/lancaster-university/microbit-dal/blob/master/source/core/MemberFunctionCallback.cpp) +* [MicroBitListener.cpp](https://github.com/lancaster-university/microbit-dal/blob/master/source/core/MicroBitListener.cpp) + +### ~ + ## Raised events Events are generated, or _raised_, for by the @boardname@ for a paired device. These are raised using the [raise event](/reference/control/raise-event) function.