docs: Prefer Jinja2 "set" directive to default_parameter_xxx in examples
The "set" directive is more flexible and easier to understand. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
@@ -163,12 +163,8 @@ that if the method takes parameters they should be provided as keyword
|
||||
arguments. Below is an example of how it may called from a gcode_macro:
|
||||
```
|
||||
[gcode_macro PANELDUE_BEEP]
|
||||
default_parameter_FREQUENCY: 300
|
||||
default_parameter_DURATION: 1.
|
||||
gcode:
|
||||
{action_call_remote_method("paneldue_beep",
|
||||
frequency=FREQUENCY|int,
|
||||
duration=DURATION|float)}
|
||||
{action_call_remote_method("paneldue_beep", frequency=300, duration=1.0)}
|
||||
```
|
||||
|
||||
When the PANELDUE_BEEP gcode macro is executed, Klipper would send something
|
||||
|
||||
Reference in New Issue
Block a user