Syntax color for a formula token, or undefined to inherit the cell's font color (operators, parens,
separators, whitespace). Reference-literal tokens (those carrying a referenceIndex — cells AND the
range operators that bind them, e.g. :) rotate through PICKER_COLORS by that index, so co-referenced ranges
share a hue — LITERALLY the same color expressions the range picker draws its rectangles with, so text
and on-grid rectangle always match, both follow light/dark for free, AND a field OUTSIDE any themed
workbook surface (a standalone dialog/panel — no --sxl-color-series-* definitions in scope) still
colors through the palette's built-in literal fallbacks. (A bare var() with no fallback computes to
nothing there — references silently rendered in the plain text color.) Keying off the SDK's
referenceIndex (not a hardcoded type list) keeps the whole span, operators included, one color while a
function that merely returns a reference stays function-colored.
Syntax color for a formula token, or
undefinedto inherit the cell's font color (operators, parens, separators, whitespace). Reference-literal tokens (those carrying areferenceIndex— cells AND the range operators that bind them, e.g.:) rotate throughPICKER_COLORSby that index, so co-referenced ranges share a hue — LITERALLY the same color expressions the range picker draws its rectangles with, so text and on-grid rectangle always match, both follow light/dark for free, AND a field OUTSIDE any themed workbook surface (a standalone dialog/panel — no--sxl-color-series-*definitions in scope) still colors through the palette's built-in literal fallbacks. (A barevar()with no fallback computes to nothing there — references silently rendered in the plain text color.) Keying off the SDK'sreferenceIndex(not a hardcoded type list) keeps the whole span, operators included, one color while a function that merely returns a reference stays function-colored.