From ab0582ff9705702f50f3bfde15d81c00f3175293 Mon Sep 17 00:00:00 2001 From: Vanessa Dannenberg Date: Fri, 17 Aug 2018 10:39:20 -0400 Subject: [PATCH] update README accordingly --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 7ddc4c7..7388310 100644 --- a/README.md +++ b/README.md @@ -49,6 +49,7 @@ The panels also respond to these control messages: * "stop_scroll" does just what it says - it stops the auto-scroll timer. * "scroll_speed" followed by a decimal number (in the string, not a byte value) sets the time between scroll steps. Minimum 0.5s, maximum 5s. * "scroll_step" will immediately advance the last-displayed message by one character. Omit the above automatic scrolling keywords, and use ONLY this keyword instead if you want to let your LuaController control the scrolling speed. +* "get" and "getstr" to read the one character (as a numerical character value) displayed by the master panel, or the last-stored message for the entire lineup/wall (from the master panel's meta), respectively. If you need vertical scrolling, you will have to handle that yourself (since the size of a screen/wall is not hard-coded). @@ -70,8 +71,6 @@ A byte value of 29 in a string signals a cursor position command. The next two b Any number of color, line feed, and cursor position commands may be present in a string, making it possible to "frame-buffer" a screen full of text into a string before printing it. -You can use "get" and "getstr" to read the one character from the connected panel. These messages will not read the other panels in the lineup/wall. - All panels emit a small amount of light when displaying something. The panels only mount on a wall.