hfVisualizer Remote Control Function
function
hfVisualizer --remote [--target <id>] function <type> <name> (--content <text> | --content-file <file>) [--unit-system <text>]
- Creates or updates one
*Functiondefinition. - Exactly one of
--contentor--content-fileis required. functionruns only in preprocessing mode.<type>and<name>must not be empty.- Optional
--unit-system <text>maps to the localUnitSystem=token on the*Functionkeyword line. - Content is passed directly to
readFunctionModification(..., true)after the IPC layer prepends the computed*Functionkeyword line. - Inside
--content, use\nfor line breaks.\\nstays literal. - Empty content is rejected.
- Successful apply marks the database modified and refreshes the render pipeline.
Example:
hfVisualizer --remote function TimeSeries TIME1 --content "0, 1\n1, 1"
hfVisualizer --remote function Tabular AMP1 --unit-system kN-mm-s-K --content-file D:\Work\function.txt
function-rename
hfVisualizer --remote [--target <id>] function-rename <old-name> <new-name>
- Available only in preprocessing mode.
- Both names must be non-empty and use the same single-token normalization as GUI edits.
- The source name must exist.
- The target name must not collide with another function unless it normalizes to the same name, in which case the command succeeds as a no-op.
- Successful execution is recorded by
script-saveas a canonicalfunction-rename ...tail.
Example:
hfVisualizer --remote function-rename TIME1 TIME_MAIN
function-delete
hfVisualizer --remote [--target <id>] function-delete <name>
- Available only in preprocessing mode.
namemust be non-empty and must resolve to an existing function.- The command uses the same delete path as ModelTree delete.
- Existing delete guards are preserved. For example, delete still fails when the function is referenced by a material.
- Successful execution is recorded by
script-saveas a canonicalfunction-delete ...tail.
Example:
hfVisualizer --remote function-delete TIME_MAIN