Add support for parametrized lua files #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for parametrization in most variables read from or written to model lua files. Input lua files may include variables wrapped in a dummy function called
Variablethat is overridden by puppeteer at load time. puppeteer will then show Lua expressions in the property browser that can be edited and previewed in real time. Invalid lua expressions are marked red and are not saved. When exporting, a valid Lua file is created that preserves the parameters.This approach is fully backwards-compatible with existing files and with RBDL, since when evaluated by a different program, the
Variable()wrapper function just does nothing and the lua file evaluates just fine.This is supported for nearly all model fields. The following properties in the property browser may not contain expressions:
Sample input file: