HiNC-Deploy/HiNC-2025-win-desktop-Deploy
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

deploy webservice static-file routing for docsite folder URLs, per-instance step-cache db, and constant-height panel title bars.

Browse Source
This commit is contained in:
iamboss
2026-08-27 14:51:37 +08:00
parent 1fc510af5e
commit 2a98ae7556
1468 changed files with 182837 additions and 18888 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/api/Hi.NcParsers.Syntaxs.html
+15 -1
View File
@@ -166,7 +166,7 @@ block, applicable to any interpolated point along the contour.</li><li><a class=
of a rotary-state-dependent transform (RTCP rotary-dynamic). Composing it
produces a correct endpoint MC, but interpolated points along the contour
must be derived per-step by motion semantics
(<a class="xref" href="Hi.NcParsers.Semantics.ClLinearMotionSemantic.html">ClLinearMotionSemantic</a>); do not apply it to
(<a class="xref" href="Hi.NcParsers.Semantics.ClLinearMcMotionSemantic.html">ClLinearMcMotionSemantic</a>); do not apply it to
interpolated ProgramXyz.</li></ul>
Both kinds carry a real Mat4d so composition stays a pure matrix product —
no entry has a missing matrix. Use <a class="xref" href="Hi.NcParsers.Syntaxs.TransformationUtil.html#Hi_NcParsers_Syntaxs_TransformationUtil_HasDynamicEntry_System_Text_Json_Nodes_JsonObject_">HasDynamicEntry(JsonObject)</a> to detect
@@ -199,6 +199,20 @@ without producing actions.</p>
<dd><p>In-situ syntax: mutates the <a class="xref" href="Hi.NcParsers.Syntaxs.SyntaxPiece.html#Hi_NcParsers_Syntaxs_SyntaxPiece_JsonObject">JsonObject</a>
of the given node in-place without changing the node count.
Most parsing and logic syntaxes implement this interface.</p>
</dd>
</dl>
<h3 id="delegates">
Delegates
</h3>
<dl class="jumplist">
<dt><a class="xref" href="Hi.NcParsers.Syntaxs.ExpressionPrefixParser.html">ExpressionPrefixParser</a></dt>
<dd><p>Longest-valid-prefix expression parse over <code class="paramref">source</code>:
returns <code>true</code> with <code class="paramref">consumedLength</code> set to the
number of leading characters forming a valid expression (the grammar
decides where a captured RHS ends), or <code>false</code> when not even a
prefix parses. Capture syntaxes take this as an optional hook so the
assignment/tag grammars stay decoupled from any concrete expression
parser (see <code>NcExpressionDialectUtil.TryParsePrefix</code>).</p>
</dd>
</dl>