Glossary
The words Round Trip uses for its source, graph, controls and visual building blocks.
On this page
Round Trip uses one name for each visible idea. Use these words when following a guide or describing a problem in support.
Branch
Section titled “Branch”A flow node with true and false execution outputs. It corresponds to a C# if, with an optional false path for else.
Canvas
Section titled “Canvas”The center of Round Trip Graphs, where the selected method appears as nodes connected by pins and wires.
Comment popup
Section titled “Comment popup”A post-it surface opened from a source comment marker on a node or pill. Other node tools may call this a node comment.
Compile
Section titled “Compile”The explicit action that validates drafts and writes supported changes to C#. Compile is the only documentation verb for that source-writing step.
Data pin
Section titled “Data pin”A typed input or output carrying a value. Its color follows the value type. Other node tools may call it a value port.
A visual edit that has not been written to C# yet. The Previewing your changes. banner marks this state.
Entry node
Section titled “Entry node”The start of a method graph. It exposes method parameters and the first exec output. Other node tools may call it a start node.
Exec pin
Section titled “Exec pin”An execution input or output that carries ordering, not a data value. Exec wires are white.
Explorer
Section titled “Explorer”The class and member browser in the left rail. It lists indexed source types with their methods and variables.
A read of a field, property, local, parameter or other value. A compact member read is usually shown as a pill.
Graph configuration file
Section titled “Graph configuration file”A .rt.json file containing arrangement and view choices such as positions, viewport, reroute knots, collapse state and comment popup placement. It is not source and does not replace the C# that produces the graph.
Hollow pin
Section titled “Hollow pin”An unwired pin with no value yet. Other node tools may call it an unset socket.
Identity header
Section titled “Identity header”The top of the right rail. It names the selected method or member and shows metadata in the form kind · access · returns.
Literal
Section titled “Literal”An inline value box on an unwired data pin. It holds a source value such as a number, Boolean, string, vector component or object reference.
A card on the canvas representing a call, statement, expression or control-flow construct. Other node tools often call the same shape a card or block.
A compact GET read node for a field, property, local, this or static value. It can fan one read to several consumers. A member chain read off a call’s result, such as collision.GetContact(i).normal.y, is one pill: y, with normal in its eyebrow, on the call’s return wire.
A connection point on a node. Pins are either exec pins or typed data pins. Other node tools may call them ports or sockets.
Placeholder node
Section titled “Placeholder node”A gray node for a source construct Round Trip cannot safely represent. A non-design placeholder refuses Compile so the unsupported code is not silently lost.
A side panel around the canvas. The left rail contains the Explorer and members. The right rail contains the identity header and inspector cards.
Reroute knot
Section titled “Reroute knot”A small point used to bend or share a wire without changing what the C# means. Other node tools may call it a reroute point.
Return node
Section titled “Return node”The method exit that supplies a return value when the method has one. The return row under flow control in the canvas menu places one, with a value pin of the method’s return type when the method returns a value. Other node tools may call it an exit node.
An impure node that assigns a field, property, local or member value.
Source
Section titled “Source”The C# file Round Trip parses and writes. Source is authoritative; the graph is a view of it.
Switch arm
Section titled “Switch arm”One case or default route of a switch statement or switch expression. Each arm holds its own match and result or execution body.
A connection between pins. White exec wires show order. Data wires take the color of their type and show value flow. Other node tools may call them edges or links.
- Nodes, pins, and wires: see the vocabulary on a real method.
- Colors: map node families and data types to their exact colors.
- C# is the truth: place source, drafts and graph configuration in the full loop.