Archived
deploy webservice static-file routing for docsite folder URLs, per-instance step-cache db, and constant-height panel title bars.
This commit is contained in:
@@ -95,16 +95,38 @@
|
||||
Classes
|
||||
</h3>
|
||||
<dl class="jumplist">
|
||||
<dt><a class="xref" href="Hi.Mappings.FileTimeSection.html">FileTimeSection</a></dt>
|
||||
<dd><p>Represents a section of a file defined by a time range.</p>
|
||||
<dt><a class="xref" href="Hi.Mappings.FileDateTimeSection.html">FileDateTimeSection</a></dt>
|
||||
<dd><p>(B) Time window expressed in absolute <a class="xref" href="https://learn.microsoft.com/dotnet/api/system.datetime">DateTime</a> only.</p>
|
||||
</dd>
|
||||
</dl>
|
||||
<h3 id="enums">
|
||||
Enums
|
||||
<dl class="jumplist">
|
||||
<dt><a class="xref" href="Hi.Mappings.FileTimecodeDateTimeSection.html">FileTimecodeDateTimeSection</a></dt>
|
||||
<dd><p>(C) Time window carrying both forms. The timecode form is authoritative for
|
||||
mapping (timecode-first); the absolute form is retained for the anchor and
|
||||
for projecting to a single-form section (<code>new FileTimecodeSection(c)</code> /
|
||||
<code>new FileDateTimeSection(c)</code>) when the two forms do not agree.</p>
|
||||
</dd>
|
||||
</dl>
|
||||
<dl class="jumplist">
|
||||
<dt><a class="xref" href="Hi.Mappings.FileTimecodeSection.html">FileTimecodeSection</a></dt>
|
||||
<dd><p>(A) Time window expressed in relative <a class="xref" href="https://learn.microsoft.com/dotnet/api/system.timespan">TimeSpan</a> timecodes only.</p>
|
||||
</dd>
|
||||
</dl>
|
||||
<h3 id="interfaces">
|
||||
Interfaces
|
||||
</h3>
|
||||
<dl class="jumplist">
|
||||
<dt><a class="xref" href="Hi.Mappings.FileTimeSection.TimeOption.html">FileTimeSection.TimeOption</a></dt>
|
||||
<dd><p>Defines options for representing time values.</p>
|
||||
<dt><a class="xref" href="Hi.Mappings.IFileTimeSection.html">IFileTimeSection</a></dt>
|
||||
<dd><p>A file plus the time window of it that maps onto a range of machining steps.
|
||||
The window is expressed in whichever form the referenced sensor file uses —
|
||||
a relative <a class="xref" href="https://learn.microsoft.com/dotnet/api/system.timespan">TimeSpan</a> timecode, an absolute <a class="xref" href="https://learn.microsoft.com/dotnet/api/system.datetime">DateTime</a>,
|
||||
or both. Concrete forms: <a class="xref" href="Hi.Mappings.FileTimecodeSection.html">FileTimecodeSection</a> (A),
|
||||
<a class="xref" href="Hi.Mappings.FileDateTimeSection.html">FileDateTimeSection</a> (B), <a class="xref" href="Hi.Mappings.FileTimecodeDateTimeSection.html">FileTimecodeDateTimeSection</a> (C).</p>
|
||||
<p>
|
||||
These are pure data carriers — turning an absolute <a class="xref" href="https://learn.microsoft.com/dotnet/api/system.datetime">DateTime</a> form
|
||||
into a relative timecode is done once at the mapping boundary against the
|
||||
project-scoped mapping anchor, not by a method here.
|
||||
</p>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user