Table of Contents

What a Run Marks

What the Program branch's file panel shows for one pass, and how a line, a chart and the tool path move the same sentence cursor. The branch's nodes, its passes, the writeback conversions, the rebuild and Recompute are on Program Branch.

The line viewer is virtualized. Text arrives in 1000-line pages covering the visible window plus two pages either side; the server caps one request at 2000 lines and keeps a small most-recently-used cache of whole files keyed on path and last-write time, so paging through a long program does not re-read it once per page. A path with no file on disk is answered as non-existent, the miss is cached so scrolling does not re-fire it, and the panel captions the file as missing — or, for an inline node, as inline text that is no longer available, because an NC Code command's text is served from the mission command itself and goes when the command is removed or retitled. A disk file wins over a command title that shadows it.

Marks are fetched the same way and per selected pass. A line the pass executed carries the sentence index it ran and the range of machining steps that sentence produced; a line absent from the answer did not execute in that pass and is greyed — but only once the node holds at least one invocation, so a placeholder's text renders plain rather than uniformly grey. A line whose sentence produced steps carries a step badge, single-valued or a range.

Marks grow as a run advances, so a page cached early would keep later lines looking unexecuted. The panel drops its mark cache and re-fetches the visible window on every throttled CL-strip update broadcast.

Clicking a line points the shared sentence cursor at that source position, which is what fills the Step Info column's Block Info panel; when the line's sentence produced steps, the click also selects that sentence's first step, moving the charts and the 3D strip with it. A line with no steps — a G54, a comment, a line that never ran — moves the cursor alone. Hovering a line sends the same anchor as the entered step on a 50 ms leading-edge throttle, and leaving the viewer clears it.

The traffic runs the other way too, on two paths. The broadcast path is shallow: any step selection, from any tab or from code, lands on the cursor, and the mounted file panel — only when its path matches — switches to that step's pass and reveals the line. The click path goes further. A step picked by a left click on a chart or on the tool path reaches the host's revealStepInProgram after the step is selected, and that call never selects a step: it switches Follow off and, when the selection is in the Program branch — the root or any node under it — resolves the step's file node, a subprogram node included, re-reading the branch once for a file or a pass the snapshot does not list yet, parks the jump and moves the selection there through requestSelect, a user act that writes ?tree=. When the step's node is the selection already, the mounted panel takes the jump through a watcher, so re-clicking the selected step scrolls the line back into view. A selection resting on Mission is not taken: that panel may hold staged edits. The reveal hangs on the click, not on the StepSelected broadcast — that reaches every tab, carries only the step index and is silent when the selected step is selected again; a 3D click is relayed by the server to the clicking canvas's connection alone (StepClicked on the rendering hub). A late answer is dropped: the reveal gives up when a user selection, the route or Follow moved while sentence-of-step was on its way. A target the panel's scroller cannot take — unsized, or hidden under a collapsed editor row — is parked and applied when the viewer regains height; the row is never expanded for it. Both paths mark the cursor's origin as a step, which is how Block Info tells a step whose play kept no block data from a line that did not run.

sentence-of-step says more than whether the step is there (with no strip it is a bare found: false). Without a step it carries stripCount, running and locked (a run is live, running or paused, so the pipeline may still fill a position), and notBuiltYet when the index is the next one a built step takes once a play began; for a built step whose sentence has no file line (a session script's act) it carries the step's sentenceIndex with found: false. A Collision--Detected is anchored to the index its pose's step takes and said before that step is built (so are the licence and lease refusals said before a step is granted and Player-Run--Fault; a Step-Task--Fault names a step whose building failed), so it can name an index no step holds yet, or, after a stop and a start without a reset, an index a later step took: the step is the message's only when the answer's sentenceIndex is the message's. The Session Info Panel reads its step rows' anchors that way, and so can a client polling GET api/Execution/messages (Replay Acceptance §5); the comparison holds within one numbering of the sentences. The other step messages are not compared: a script's, a tool change's, a line end's and an empty spindle's are anchored to the next built step by design, and a stroke-limit report, which names no sentence, to the step it checked, or to the next built step when the motion it checked built none.

Follow is the live variant. It lives on the Program row of the Control Tree, not in a panel, because it is cross-file: while it is on, the host moves the selection to the file node the execution-status hub's cursor is in — re-reading the branch for a file or a pass it has not listed yet — and the file panel switches to the executing pass, scrolls to the executing line and shows a read-only following badge. It is off by default and session-only, outside stored preferences, since a flag that survived a reload would seize the next run's selection. Any selection of the user's own switches it off — a tree node, a chart or tool-path click, a line click in the viewer — and while it drives, the selection moves without writing ?tree=.

The files behind the viewer, the cursor and Follow are listed on Program Branch.

See Also

  • Program Branch — the branch this viewer belongs to: its nodes, passes, writeback conversions, rebuild and Recompute
  • Block Info Panel — the Step Info panel a line click here fills, and what the syntax piece gives it
  • Execution Page — the page that hosts the branch, and the charts and tool path a click there reveals in this viewer