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.ParsingSyntaxs.Heidenhain.HeidenhainLblSyntax.html
+27 -1
View File
@@ -6,7 +6,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="title" content="Class HeidenhainLblSyntax | HiAPI-C# 2025 ">
<meta name="description" content="Syntax for Heidenhain LBL command (label definition). Label can be a number (1-65535) or a text name (e.g., &amp;ldquo;MyLabel&amp;rdquo;). LBL 0 is reserved for end of subprogram.">
<meta name="description" content="Syntax for Heidenhain LBL command (label definition). Label can be a number (1-65535) or a text name (e.g., &amp;ldquo;MyLabel&amp;rdquo;). LBL 0 is reserved for end of subprogram. Only a DEFINITION is captured: CALL LBL (any spacing) and the FN 9–12 jump spellings (GOTO LBL n, glued GOTOLBL) are excluded — this syntax doubles as the label-scan probe of the P4 call machinery, where mistaking a jump line (or the call line itself) for a definition splices the wrong program section.">
<link rel="icon" href="../img/HiAPI.favicon.ico">
<link rel="stylesheet" href="../public/docfx.min.css">
<link rel="stylesheet" href="../public/main.css">
@@ -100,6 +100,13 @@ Class HeidenhainLblSyntax
<div class="markdown summary"><p>Syntax for Heidenhain LBL command (label definition).
Label can be a number (1-65535) or a text name (e.g., &ldquo;MyLabel&rdquo;).
LBL 0 is reserved for end of subprogram.</p>
<p>
Only a DEFINITION is captured: <code>CALL LBL</code> (any spacing) and the
FN 9–12 jump spellings (<code>GOTO LBL n</code>, glued <code>GOTOLBL</code>) are
excluded — this syntax doubles as the label-scan probe of the P4 call
machinery, where mistaking a jump line (or the call line itself) for
a definition splices the wrong program section.
</p>
</div>
<div class="markdown conceptual"></div>
@@ -203,6 +210,25 @@ LBL 0 is reserved for end of subprogram.</p>
"LBL": { "Name": "0" }
}
}</code></pre>
<p>#BeforeBuild.UnparsedText: <code>LBL &ldquo;SLOW_FEED&rdquo;</code> (quotes are stripped from the captured name)
#AfterBuild:</p>
<pre><code class="lang-csharp">{
"Parsing": {
"LBL": { "Name": "SLOW_FEED" }
}
}</code></pre>
<p>#BeforeBuild.UnparsedText: <code>FN 12: IF +Q1 LT +5 GOTO LBL 5</code> (a jump target, not a definition — the line is left whole for the FN jump family)
#AfterBuild:</p>
<pre><code class="lang-csharp">{
"UnparsedText": "FN 12: IF +Q1 LT +5 GOTO LBL 5"
}</code></pre>
<p>#BeforeBuild.UnparsedText: <code>G98 L1</code> (the DIN/ISO definition twin — the G98/L pair is claimed together, so no G98 flag leaks to the numbered-flag capture)
#AfterBuild:</p>
<pre><code class="lang-csharp">{
"Parsing": {
"LBL": { "Name": "1" }
}
}</code></pre>