Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ego_script [2026/07/22 20:16] hermann |
ego_script [2026/07/22 20:26] (current) hermann |
||
|---|---|---|---|
| Line 526: | Line 526: | ||
| Converting abbreviated syntax to verbose is always lossless. Converting verbose to abbreviated is only possible when all hooks are free of comments, properties, and identifiers that do not appear in the expression. | Converting abbreviated syntax to verbose is always lossless. Converting verbose to abbreviated is only possible when all hooks are free of comments, properties, and identifiers that do not appear in the expression. | ||
| - | > **Note:** This distinction only affects saved or generated script text. The graphical interface itself always displays and edits a calculator functor's expression using the verbose ''i1''/''t1''/''v1'' style, with each hook shown as its own node, regardless of whether the //Use abbreviated syntax// option is enabled or what form the underlying file used. The ''#name''/''%name'' abbreviated form exists only in the text; there is no abbreviated view inside the GUI. | + | > **Note:** This distinction applies only to saved or generated script text. The graphical interface always displays and edits a calculator functor's expression in the verbose ''i1''/''t1''/''v1'' form, with each hook represented as its own functor node, regardless of whether the //Use abbreviated syntax// option is enabled or which form the underlying file uses. The ''#name''/''%name''/''$name'' abbreviated form exists only in script text; the graphical interface has no corresponding abbreviated representation. |
| A common situation where this matters: if you connect a map or lookup table purely to define the output format — not because it is referenced in the expression — connecting it via a ''NumberMap'' or ''NumberTable'' hook will block abbreviated syntax, since the hook defines an identifier absent from the expression. Use the dedicated port instead: the ''Result Format'' input port for map calculators, or the ''Base Lookup Table'' input port for lookup table calculators. These connections do not create hooks and do not affect the availability of abbreviated syntax. | A common situation where this matters: if you connect a map or lookup table purely to define the output format — not because it is referenced in the expression — connecting it via a ''NumberMap'' or ''NumberTable'' hook will block abbreviated syntax, since the hook defines an identifier absent from the expression. Use the dedicated port instead: the ''Result Format'' input port for map calculators, or the ''Base Lookup Table'' input port for lookup table calculators. These connections do not create hooks and do not affect the availability of abbreviated syntax. | ||