Deployed 9726d83 with MkDocs version: 1.5.3

index.html

@@ -290,6 +290,40 @@
     What is different
   </a>
 
+    <nav class="md-nav" aria-label="What is different">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#general" class="md-nav__link">
+    General
+  </a>
+
+</li>
+
+          <li class="md-nav__item">
+  <a href="#exassetintshiftlistui" class="md-nav__link">
+    exAssetIntShiftListUI
+  </a>
+
+</li>
+
+          <li class="md-nav__item">
+  <a href="#exassetintjoblistui" class="md-nav__link">
+    exAssetIntJobListUI
+  </a>
+
+</li>
+
+          <li class="md-nav__item">
+  <a href="#exassetinttimelineui" class="md-nav__link">
+    exAssetIntTimelineUI
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
 </li>
 
           <li class="md-nav__item">
@@ -470,12 +504,29 @@ <h3 id="what-is-missing">What is missing</h3>
 <li>There is no integration for mappAlarmX. Since the official version only supported 3 alarms this was removed. The community version provides a rich set of status information that can be used to trigger alarms. See <a href="appendix.html">appendix</a> for the corresponding error numbers and the <a href="faq/faq.html">FAQ</a> for more information.</li>
 </ul>
 <h3 id="what-is-different">What is different</h3>
+<h4 id="general">General</h4>
 <ul>
 <li>The beginning of all function block names was changed from Mp to ex. For example MpAssetIntCore was changed to exAssetIntCore.</li>
 <li>The beginning of all data type names was changed from Mp to ex. For example MpAssetIntCoreInfoType was changed to exAssetIntCoreInfoType. The new structures are identical to the official structures. All exceptions are documented in the <a href="compatibility/compatibility.html">compatibility</a> page.</li>
 <li>Instead of the MpLink all function blocks use a pointer to a remanent variable of type exAssetIntLinkType. This structure is used for cross function block communication.</li>
 <li>All data is stored in a ring buffer consisting of individual files. Each file contains one event. An event can be job or shift change or a downtime event. You can find more details about the data management in the <a href="appendix.html">appendix</a>.</li>
 </ul>
+<h4 id="exassetintshiftlistui">exAssetIntShiftListUI</h4>
+<ul>
+<li>The parameter UISetup.OutputListSize was removed. The list size is now defined by the constant UI_SHIFT_LIST_IDX.</li>
+<li>The parameter UISetup.SortingStartTime was added to allow for ascending and descending sorting.</li>
+</ul>
+<h4 id="exassetintjoblistui">exAssetIntJobListUI</h4>
+<ul>
+<li>The parameter UISetup.OutputListSize was removed. The list size is now defined by the constant UI_JOB_LIST_IDX.</li>
+<li>The parameter UISetup.SortingStartTime was added to allow for ascending and descending sorting.</li>
+</ul>
+<h4 id="exassetinttimelineui">exAssetIntTimelineUI</h4>
+<ul>
+<li>The parameter UISetup.TimelineListSize was removed. The list size is now defined by the constant UI_SHIFT_TIMELINE_IDX.</li>
+<li>The parameter UISetup.SortingStartTime was added to allow for ascending and descending sorting.</li>
+<li>All parameters from UIConnect.Output.Display were move one level up to UIConnect.Output to harmonize the data with the other function blocks.</li>
+</ul>
 <h3 id="what-is-new">What is new</h3>
 <ul>
 <li>Most function blocks have an additional Logger input. This is used to log messages to the console. This is useful for debugging purposes.</li>