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

fix bug of cubetree init SAT and triangles-tip-cube-corner margin case.

Browse Source
This commit is contained in:
iamboss
2026-03-25 12:40:37 +08:00
parent ff2cfa6210
commit 8aa17a0280
58 changed files with 1123 additions and 986 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/api/Hi.NcParsers.Syntaxs.SyntaxPiece.html
+12
View File
@@ -170,6 +170,18 @@ Class SyntaxPiece
<h2 id="Hi_NcParsers_Syntaxs_SyntaxPiece_remarks">Remarks</h2>
<div class="markdown level0 remarks"><p>The design pattern of <a class="xref" href="Hi.NcParsers.Syntaxs.SyntaxPiece.html#Hi_NcParsers_Syntaxs_SyntaxPiece_Sentence">Sentence</a> and <a class="xref" href="Hi.NcParsers.Syntaxs.SyntaxPiece.html#Hi_NcParsers_Syntaxs_SyntaxPiece_JsonObject">JsonObject</a> are one-one mapping.</p>
<p><b>JSON value type convention:</b>
Prefer base types (double, int) over string for numeric values in <a class="xref" href="Hi.NcParsers.Syntaxs.SyntaxPiece.html#Hi_NcParsers_Syntaxs_SyntaxPiece_JsonObject">JsonObject</a>.
This applies to both parsing syntaxes and logic syntaxes.
Strings should only be used when the value is genuinely textual
(e.g., macro variable references like "#1", "Q2", coordinate IDs like "G54")
or when the value cannot be parsed to a number.
Use <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.FloatTagSetupSyntax.html">FloatTagSetupSyntax</a>,
<a class="xref" href="Hi.NcParsers.ParsingSyntaxs.IntegerTagSetupSyntax.html">IntegerTagSetupSyntax</a>,
or <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.ParameterizedFlagSyntax.html#Hi_NcParsers_ParsingSyntaxs_ParameterizedFlagSyntax_FloatParamPrefixes">FloatParamPrefixes</a>
/ <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.ParameterizedFlagSyntax.html#Hi_NcParsers_ParsingSyntaxs_ParameterizedFlagSyntax_IntParamPrefixes">IntParamPrefixes</a>
to store typed values at parse time.
</p>
</div>