Idea:
- adding "/report/commands/entry/argument, [cmd_index], [arg_index], [minval], [maxval], [warp], [step], [default], [units]"
But perhaps wise to simplify and not leverage every possible item…
we need a system to get feedback from the engine. for example:
- sound output levels (for a VU display)
- sample playback position (for building an mlr-like thing)
i'm figuring this is a matter…
when `matron` receives a lua code string, it simply tries to evaluate it as a complete chunk. it should be smarter, to accomodate continuation lines.
see lua source code:
https://github.com/lua/l…