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

deploy.

Browse Source
This commit is contained in:
iamboss
2026-09-12 18:16:27 +08:00
parent b7f55aa631
commit 397a7a8cc4
96 changed files with 1167 additions and 1259 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/api/Hi.MachiningProcs.MachiningActRunner.html
+3 -1
View File
@@ -1058,8 +1058,10 @@ Internal Use Only.</p>
<div class="markdown level1 summary"><p>Emit one-shot session <code>ConfigurationError</code>s naming the root cause when the
currently equipped tool's <a class="xref" href="Hi.Milling.Cutters.MillingCutter.html">MillingCutter</a> has an unreasonable
upper-beam / shank geometry (see
<a class="xref" href="Hi.Milling.Cutters.MillingCutter.html#Hi_Milling_Cutters_MillingCutter_GetUpperBeamGeometryIssues">GetUpperBeamGeometryIssues()</a>) — e.g. an
<a class="xref" href="Hi.Milling.Cutters.MillingCutter.html#Hi_Milling_Cutters_MillingCutter_ReportUpperBeamGeometryIssues_System_IProgress_Hi_Common_Messages_IMessage__System_Object_">ReportUpperBeamGeometryIssues(IProgress&lt;IMessage&gt;, object)</a>) — e.g. an
<code>ExtendedCylinder</code> beam whose <code>FullLength</code> sits below the flute height.
The error's wording is the cutter's own literal emit, shared with the web API's
edit-time warnings, so the tool it belongs to rides in the detail payload.
Before this check, such a setting surfaced only as a per-step
<code>NullReferenceException</code> cascade inside the thermal physics, with nothing
naming the beam. Additionally emits a <code>Cutter-Shank&ndash;ThermalModelUnavailable</code>