led: Support automated LED updates based on display_template results

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
Kevin O'Connor
2022-03-23 18:06:09 -04:00
parent a6ab56c0a6
commit 1ab3ac39e4
3 changed files with 126 additions and 10 deletions

View File

@@ -3552,12 +3552,18 @@ text:
### [display_template]
Display data text "macros" (one may define any number of sections with
a display_template prefix). This feature allows one to reduce
repetitive definitions in display_data sections. One may use the
builtin render() function in display_data sections to evaluate a
template. For example, if one were to define `[display_template
my_template]` then one could use `{ render('my_template') }` in a
display_data section.
a display_template prefix). See the
[command templates](Command_Templates.md) document for information on
template evaluation.
This feature allows one to reduce repetitive definitions in
display_data sections. One may use the builtin `render()` function in
display_data sections to evaluate a template. For example, if one were
to define `[display_template my_template]` then one could use `{
render('my_template') }` in a display_data section.
This feature can also be used for continuous LED updates using the
[SET_LED_TEMPLATE](G-Codes.md#set_led_template) command.
```
[display_template my_template_name]
@@ -3570,9 +3576,9 @@ display_data section.
# "param_speed = 75" might have a caller with
# "render('my_template_name', param_speed=80)". Parameter names may
# not use upper case characters.
#text:
# The text to return when the render() function is called for this
# template. This field is evaluated using command templates (see
text:
# The text to return when the this template is rendered. This field
# is evaluated using command templates (see
# docs/Command_Templates.md). This parameter must be provided.
```