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

fix SoftNcRunner GM code normalization.

Browse Source
This commit is contained in:
iamboss
2026-05-06 13:21:19 +08:00
parent 0fe9497552
commit 2f57932000
1238 changed files with 69405 additions and 22511 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/api/Hi.NcParsers.ParsingSyntaxs.html
+44 -3
View File
@@ -94,9 +94,34 @@
<h3 id="classes">
Classes
</h3>
<dl class="jumplist">
<dt><a class="xref" href="Hi.NcParsers.ParsingSyntaxs.BlockSkipSyntax.html">BlockSkipSyntax</a></dt>
<dd><p>Parses the ISO 6983 / Fanuc Block Delete (a.k.a. Block Skip) prefix
<code>/</code> or <code>/N</code> (N = 1..9) at the head of an NC block.</p>
<p>
Behaviour:
<ul><li>No leading <code>/</code> → no-op, no <a class="xref" href="Hi.NcParsers.Keywords.BlockSkip.html">BlockSkip</a> section
is written.</li><li><code>/</code> with <a class="xref" href="Hi.NcParsers.Dependencys.IBlockSkipConfig.html">IBlockSkipConfig</a> layer OFF (or the
dependency absent) → prefix is consumed, <a class="xref" href="Hi.NcParsers.Keywords.BlockSkip.html">BlockSkip</a>
<a class="xref" href="Hi.NcParsers.Keywords.BlockSkip.html#Hi_NcParsers_Keywords_BlockSkip_Symbol">Symbol</a>/<a class="xref" href="Hi.NcParsers.Keywords.BlockSkip.html#Hi_NcParsers_Keywords_BlockSkip_Layer">Layer</a> recorded
for audit, <a class="xref" href="Hi.NcParsers.Keywords.BlockSkip.html#Hi_NcParsers_Keywords_BlockSkip_Body">Body</a> stays null; the rest of the
block stays in <code>UnparsedText</code> and parses normally.</li><li><code>/</code> with layer ON → the remaining block text is moved
from <code>UnparsedText</code> into <a class="xref" href="Hi.NcParsers.Keywords.BlockSkip.html#Hi_NcParsers_Keywords_BlockSkip_Body">Body</a> and
<code>UnparsedText</code> is cleared. Downstream parsing syntaxes see no
NC text so they emit nothing; semantics therefore produce no act.
Must run <i>after</i> comment / CsScript syntaxes so that comments
(and CsScript embedded in comments) continue to take effect
regardless of the skip switch.</li></ul>
</dd>
</dl>
<dl class="jumplist">
<dt><a class="xref" href="Hi.NcParsers.ParsingSyntaxs.CsScriptSyntax.html">CsScriptSyntax</a></dt>
<dd></dd>
<dd><p>Extracts C# script markers from the oral content of a comment.
<a class="xref" href="Hi.NcParsers.ParsingSyntaxs.CsScriptSyntax.html#Hi_NcParsers_ParsingSyntaxs_CsScriptSyntax_PreMarker">PreMarker</a> marks a script that runs before the NC block;
<a class="xref" href="Hi.NcParsers.ParsingSyntaxs.CsScriptSyntax.html#Hi_NcParsers_ParsingSyntaxs_CsScriptSyntax_PostMarker">PostMarker</a> marks a script that runs after.
The symbols are configurable and serialized to XML.</p>
</dd>
</dl>
<dl class="jumplist">
<dt><a class="xref" href="Hi.NcParsers.ParsingSyntaxs.FlagSyntax.html">FlagSyntax</a></dt>
@@ -111,7 +136,8 @@ Variable text (e.g. Q2, #1, [#1+#2]) remains as <a class="xref" href="https://le
</dl>
<dl class="jumplist">
<dt><a class="xref" href="Hi.NcParsers.ParsingSyntaxs.HeadIndexSyntax.html">HeadIndexSyntax</a></dt>
<dd></dd>
<dd><p>Parses a leading block index (e.g. Heidenhain line numbers) after an optional <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.HeadIndexSyntax.html#Hi_NcParsers_ParsingSyntaxs_HeadIndexSyntax_HeadSymbol">HeadSymbol</a> prefix.</p>
</dd>
</dl>
<dl class="jumplist">
<dt><a class="xref" href="Hi.NcParsers.ParsingSyntaxs.IntegerTagValueSyntax.html">IntegerTagValueSyntax</a></dt>
@@ -131,6 +157,15 @@ rather than {prefix}{digits}.</p>
<dd><p>Syntax for numbered flags (prefix + number) with optional decimal support.
<a class="xref" href="Hi.NcParsers.ParsingSyntaxs.NumberedFlagSyntax.html">NumberedFlagSyntax</a> often should place after something like <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.ParameterizedFlagSyntax.html">ParameterizedFlagSyntax</a>.
Since <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.NumberedFlagSyntax.html">NumberedFlagSyntax</a> is easy to eat those kind of flags.</p>
<p>
Single-digit integer codes are zero-padded to canonical 2-digit form
(e.g. <code>M6</code> → <code>M06</code>, <code>G0</code> → <code>G00</code>, <code>M3</code> → <code>M03</code>)
so that downstream logic syntaxes comparing against
<a class="xref" href="Hi.NcParsers.Keywords.Generic.IsoKeywords.html">IsoKeywords</a> constants (which are always
2-digit form like <a class="xref" href="Hi.NcParsers.Keywords.Generic.IsoKeywords.html#Hi_NcParsers_Keywords_Generic_IsoKeywords_M06">M06</a>) can
match Fanuc-style omitted-leading-zero codes. Two-digit and decimal
codes are kept as-is.
</p>
</dd>
</dl>
<dl class="jumplist">
@@ -139,6 +174,12 @@ Since <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.NumberedFlagSyntax.html"
This is essentially a combination of main flag matching (like <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.NumberedFlagSyntax.html">NumberedFlagSyntax</a>)
plus scoped <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.TagValueSyntax.html">TagValueSyntax</a> for the parameters after the main flag.
Note that the <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.ParameterizedFlagSyntax.html">ParameterizedFlagSyntax</a> often should be applied before <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.NumberedFlagSyntax.html">NumberedFlagSyntax</a> since <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.NumberedFlagSyntax.html">NumberedFlagSyntax</a> may eat the text that <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.ParameterizedFlagSyntax.html">ParameterizedFlagSyntax</a> should handle.</p>
</dd>
</dl>
<dl class="jumplist">
<dt><a class="xref" href="Hi.NcParsers.ParsingSyntaxs.ProgramBoundarySyntax.html">ProgramBoundarySyntax</a></dt>
<dd><p>Detects program boundary markers: leading <code>%</code> tape header or <code>O</code> program number after a prior boundary,
and records them under <a class="xref" href="Hi.NcParsers.Keywords.ProgramBoundary.html">ProgramBoundary</a> on the block JSON.</p>
</dd>
</dl>
<dl class="jumplist">
@@ -149,7 +190,7 @@ When a tag value has no decimal point (e.g. <code>Y20</code>), it is shrunk by
the implied decimal places: <code>Y20</code> → <code>Y0.020</code> (3 decimal places).
Values that already contain a decimal point are left unchanged.</p>
<p>
Place inside <a class="xref" href="Hi.NcParsers.Syntaxs.BundleSyntax.html">BundleSyntax</a> before FloatTagSetupSyntax
Place inside <a class="xref" href="Hi.NcParsers.Syntaxs.BundleSyntax.html">BundleSyntax</a> before <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.FloatTagValueSyntax.html">FloatTagValueSyntax</a>
so the modified text is parsed correctly by subsequent syntaxes.
</p>
</dd>