beckhoff-xts-viewer-3d 0.3.1 → 2.0.0

package/README.md

@@ -25,26 +25,26 @@ import { XtsViewer3D } from 'beckhoff-xts-viewer-3d';
   config={{
     processingUnits: [
       {
-        index: 0,
+        objectId: 0,
         moverType: 'AT9014_0055',
         parts: [
           {
+            objectId: 0,
             globalNumber: 0,
-            index: 0,
             modules: [
-              { moduleType: 'AT2001_0250' },
-              { moduleType: 'AT2000_0250' },
-              { moduleType: 'AT2050_0500' },
-              { moduleType: 'AT2050_0501' },
-              { moduleType: 'AT2001_0250' },
-              { moduleType: 'AT2000_0250' },
-              { moduleType: 'AT2050_0500' },
-              { moduleType: 'AT2050_0501' },
+              { moduleType: 'AT2001_0250', globalNumber: 1 },
+              { moduleType: 'AT2000_0250', globalNumber: 2 },
+              { moduleType: 'AT2050_0500', globalNumber: 3 },
+              { moduleType: 'AT2050_0501', globalNumber: 4 },
+              { moduleType: 'AT2001_0250', globalNumber: 5 },
+              { moduleType: 'AT2000_0250', globalNumber: 6 },
+              { moduleType: 'AT2050_0500', globalNumber: 7 },
+              { moduleType: 'AT2050_0501', globalNumber: 8 },
             ],
           },
         ],
         movers: [
-          { moverIndex: 0, id: 'mover-0', partOid: 0, partPositionMm: 200 },
+          { index: 0, id: 0, partOid: 0, partPositionMm: 200 },
         ],
       },
     ],
@@ -137,8 +137,10 @@ reflections, ACES tone mapping and anisotropic textures are on by default.
 - **CAD ViewCube** — opt-in, snap to standard orthogonal views.
 - **Imperative ref API** — `zoomToFit` / `setCamera` / `getCamera` /
   `getMoverWorldTransform` / `getBoundingBox` / `exportModel` /
-  `exportScreenshot` / `setMoverPosition(s)` / `getMoverPosition` /
-  `checkMoverCollisions` / `reloadAssets`.
+  `exportScreenshot` / `setMoverPosition(s)` (Record or
+  `MoverPositionEntry[]` indexed by `MoverConfig.index`) / `getMoverPosition` /
+  `setModuleStatuses` / `clearModuleStatuses` / `checkMoverCollisions` /
+  `reloadAssets`.
 - **Designed for scale** — the `⚡ Perf stress` demo runs three ovals × 250
   movers each (= 750 simultaneously animated movers) without React commits
   during the steady state.
@@ -254,7 +256,7 @@ function App() {
   useEffect(() => {
     let raf = 0;
     const tick = (t: number) => {
-      viewerRef.current?.setMoverPosition('mover-0', (t / 5) % 3000);
+      viewerRef.current?.setMoverPosition(0, (t / 5) % 3000);
       raf = requestAnimationFrame(tick);
     };
     raf = requestAnimationFrame(tick);
@@ -434,12 +436,12 @@ areas, stops, ghosts, and `getMoverWorldTransform` all follow:
 ```tsx
 processingUnits: [
   {
-    index: 0,
+    objectId: 0,
     moverType: 'AT9014_0055',
     positionFrame: { direction: 'negative', originMm: 1500 },
     parts: [/* … */],
     movers: [
-      { moverIndex: 0, id: 'mover-0', partOid: 0, partPositionMm: 0 },
+      { index: 0, id: 0, partOid: 0, partPositionMm: 0 },
     ],
   },
 ]
@@ -526,16 +528,6 @@ Webpack / Next.js: alias `three` to your root `node_modules/three`. See
 for the full snippets and how to bust Vite's pre-bundle cache after the
 change.
 
-### Known harmless console warnings
-
-- **`THREE.Clock: This module has been deprecated. Please use THREE.Timer instead.`**
-  — emitted by `@react-three/fiber`'s root-store factory
-  (`new THREE.Clock()` inside its internal `events-*.esm.js`). three.js
-  deprecated `Clock` in r183; functional behaviour is unchanged and
-  frame timing still works correctly. The warning will disappear once
-  r3f migrates its root store to `THREE.Timer`. Not actionable on the
-  consumer side; safe to ignore.
-
 ---
 
 ## Documentation