Skip to content

hfVisualizer Remote Control History

history

hfVisualizer --remote [--target <id>] history <History|PostHistory> <name> (--content <text> | --content-file <file>)
  • Creates or updates one *History or *PostHistory definition.
  • Exactly one of --content or --content-file is required.
  • <type> must be History or PostHistory.
  • <name> must not be empty.
  • Content is passed directly to readHistoryModification(..., true) after the IPC layer prepends the computed *History or *PostHistory keyword line.
  • Inside --content, use \n for line breaks. \\n stays literal.
  • Empty content is rejected.
  • Existing history items are updated in place, preserving their current list position.
  • In preprocessing mode, a successful apply refreshes the render pipeline and marks the database modified.
  • In postprocessing mode, only <type>=PostHistory is allowed. This is one of the few GUI-matched definition exceptions that remain editable there.
  • In postprocessing mode, a successful apply additionally runs runLastPostHistory() and updates the DB file immediately, matching the GUI History widget behavior.
  • Reader rule reminder:
  • first data line is the target step list
  • second and later data lines are history requests
  • at least two data lines are required after the keyword line

Example:

hfVisualizer --remote history History H1 --content "STEP1, STEP2\nD.X@10, FK.X@10\nA.X@center_line"
hfVisualizer --remote history PostHistory HPOST --content-file D:\Work\post-history.txt

history-rename

hfVisualizer --remote [--target <id>] history-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 history unless it normalizes to the same name, in which case the command succeeds as a no-op.
  • Successful execution is recorded by script-save as a canonical history-rename ... tail.

Example:

hfVisualizer --remote history-rename H1 H_MAIN

history-delete

hfVisualizer --remote [--target <id>] history-delete <name>
  • Available only in preprocessing mode.
  • name must be non-empty and must resolve to an existing history.
  • The command uses the same delete path as ModelTree delete. Remote delete intentionally stays out of the postprocessing confirmation flow and therefore remains preprocessing-only.
  • Successful execution is recorded by script-save as a canonical history-delete ... tail.

Example:

hfVisualizer --remote history-delete H_MAIN