From 0ab757de9d22a1a51f982be82908bf177eed58ab Mon Sep 17 00:00:00 2001 From: echicken <echicken@bbs.electronicchicken.com> Date: Tue, 30 Apr 2024 05:17:08 +0000 Subject: [PATCH] Clean up some debug output; notes re: writeDelay; queue stuff. --- README.md | 2 ++ readme.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/README.md b/README.md index 69c3bd5..da22dae 100644 --- a/README.md +++ b/README.md @@ -181,6 +181,8 @@ while (n < 5000) { js.do_callbacks = true; ``` +*(You can put `js.do_callbacks = true;` anywhere, but I prefer it at the end of the script as a matter of form.)* + ##### Handlers vs. Callbacks Serveral `*Device` methods accept a `responseHandler` parameter, which is a `packetHandler` function that accepts a single `MeshPacket` as a parameter. The `responseHandler` is typically optional, but if supplied it will be called when a packet is received in response to this message. diff --git a/readme.md b/readme.md index 6d9eb47..1b5cfd4 100644 --- a/readme.md +++ b/readme.md @@ -153,6 +153,8 @@ while (n < 5000) { js.do_callbacks = true; ``` +*(You can put `js.do_callbacks = true;` anywhere, but I prefer it at the end of the script as a matter of form.)* + #### Handlers vs. Callbacks Serveral `*Device` methods accept a `responseHandler` parameter, which is a `packetHandler` function that accepts a single `MeshPacket` as a parameter. The `responseHandler` is typically optional, but if supplied it will be called when a packet is received in response to this message. -- GitLab