From e8c0fa93ca8529f6440b7e75125e023e91517951 Mon Sep 17 00:00:00 2001 From: Vanessa Dannenberg Date: Fri, 17 Aug 2018 10:44:13 -0400 Subject: [PATCH] more clarifications --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 7388310..afaae7e 100644 --- a/README.md +++ b/README.md @@ -49,7 +49,8 @@ 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. +* "get" will read the one character (as a numerical character value) currently displayed by the master panel (by reading its node name) +* "getstr" will read the last-stored message for the entire lineup/wall (from the master panel's meta), respectively. Note that even if the message has been or is being scrolled, you'll get the original stored message. If you need vertical scrolling, you will have to handle that yourself (since the size of a screen/wall is not hard-coded).