Evaluation order
Variables exist for everything after them in evaluation order. Order is visual, not the order you inserted the regions, and not a hidden dependency graph.
How order is decided
- Only body regions that define or consume values take part: math, lists, sliders, and 2D frames. Header and footer bands are skipped.
- Calculeaf groups regions that sit on the same visual row — their vertical ranges overlap enough, and they are not too far apart horizontally.
- Rows run top to bottom.
- Inside a row, regions run left to right.
That matches how you read a calculation note. Two assignments on one line evaluate left first, even if the right-hand block’s box is a few pixels higher because the math rendered taller.
Evaluate All
Typing updates the region you are in. To refresh the whole chain — after a paste, a unit-system change, or a list selection — use Evaluate on the Home tab (tooltip: Evaluate All) or Ctrl+Enter .
Lists and sliders inject their current values at their place in this order.
A 2D frame injects its result names when it sits in the sequence.
Names defined with := follow
variables and scope.