deploy.

2026-09-12 18:16:27 +08:00
parent b7f55aa631
commit 397a7a8cc4
96 changed files with 1167 additions and 1259 deletions
@@ -323,6 +323,24 @@ geometry's true bounds — instead of meshing, and <code>GeomCombination</code>
 contributes nothing to a bounds query; generate the mesh yourself if you need its true extent.
 <code>MillingCutter</code>'s cutter-height bookkeeping likewise reads the profile's ZR contour and the
 upper beam's box instead of meshing both on every cache clear.</li>
+<li><strong>The web application's Legacy-Controller page</strong> — <code>HiNC-2025-webservice</code> removes the page the
+Page menu's third group opened, at <code>/controller/&lt;tab&gt;</code>, on 2026-09-11 (the 3.2 line). It edited
+<a class="xref" href="../../api/Hi.Numerical.HardNcEnv.html">HardNcEnv</a> — the project's <a class="xref" href="../../api/Hi.MachiningProcs.MachiningProject.html#Hi_MachiningProcs_MachiningProject_NcEnv">NcEnv</a>,
+the HardNc controller model that is deprecating now that
+<a class="xref" href="../../api/Hi.MachiningProcs.LocalProjectService.html#Hi_MachiningProcs_LocalProjectService_EnableSoftNcRunner">EnableSoftNcRunner</a> defaults to <code>true</code>. Controller
+settings are edited on the General Setup page's Controller branch
+(<code>/general-setup?tree=equipment/controller</code>), the SoftNc runner's own face — see
+<a href="../../manual/setup/controller.html">Controller</a>. Of the settings only that page could edit, three were
+HardNcEnv's alone and retire with it: <code>EnableShortestRotary</code> (the runner honours the program's own
+M126 / M127 modal codes), <code>MaxRotarySpeedABC</code> (the runner's rotary ceiling is the rotary rate on
+the branch's Rapid Feedrates leaf) and <code>HeidenhainMasterAxisChar</code> (a HardNc parser setting with no
+SoftNc counterpart). The fourth, <strong>Align P0</strong> — moving the part so that program zero lands on a
+work-coordinate row — is <strong>not offered on the runner path</strong>: the Work Coordinates leaf carries only
+<strong>P0</strong> and <strong>M0</strong>, which write the row from the machine position; the part is placed by hand
+instead — see <a href="../../manual/setup/program-zero-alignment.html">Program Zero Alignment</a>. Old links keep
+working: <code>/controller</code> and anything below it redirects to the Controller branch. Nothing on the
+C# side moves — <code>MachiningProject.NcEnv</code> still loads and the <code>/api/Controller/*</code> endpoints stay
+mounted, so a host that drives HardNcEnv through the API or a script is unaffected.</li>
 </ul>
 <h2 id="7-signature-and-shape-changes">7. Signature and shape changes</h2>
 <ul>
@@ -393,6 +411,15 @@ names: <code>MachineTool/Table-B1.default</code> and <code>MachineTool/CT-350.de
 renamed outright — its <code>.mt</code>, its <code>.general-mech</code> and its STL headers travel with it — and the
 duplicated nested STL set inside the CT-350 package is deleted. A project, script or <code>.mt</code> that
 refers to a shipped machine-tool package by its earlier path must be repointed at the name above.</li>
+<li><strong>The shipped mechanism file takes the canonical extension.</strong> <code>MachineTool/Table-B1.default/Table-B1.general-mech</code>
+is now <code>Table-B1.GeneralMechanism</code> — the spelling <code>GeneralMechanism.XName</code> gives and every Save As
+has written since the type-name extensions arrived — and the package's <code>Table-B1.mt</code> is repointed at
+it. <code>.general-mech</code> stays readable everywhere: the loader dispatches on the XML root element and
+never reads the extension, so a hand-authored file keeps its name and loads as before. Only something
+that refers to the shipped mechanism by its old file name must be repointed. The rename ships from
+HiNc-Resource 3.2.21; 3.2.20 still carries <code>.general-mech</code>, and an admin folder already seeded by it
+is re-mirrored — old name deleted, new name copied, <code>Table-B1.mt</code> refreshed — on the first start with
+the newer package.</li>
 </ul>

 </article>