How can I update this code to vtk.js version 28?

Javi-r · September 14, 2023, 11:44am

I want to upgrade this to vtk.js v28

const wobj = resliceCursorWidget.updateReslicePlane(
  obj.reslice,
  xyzToViewType[obj.id]
);
lineWidget.getManipulator().setOriginFrom(wobj.origin);
lineWidget.getManipulator().setNormalFrom(resliceCursorWidget.getWidgetState().getPlanes()[xyzToViewType[obj.id]].normal);

updateReslicePlane no longer returns wobj now only returns true or false
setOriginFrom and setNormalFrom no longer exist

Sebastien_Jourdain · September 15, 2023, 1:51am

github.com

Kitware/vtk-js/blob/master/BREAKING_CHANGES.md

## From 27.x to 28

- **vtkManipulator.handleEvent**: Change all `handleEvent` signatures of manipulators. Used to be `handleEvent(callData, glRenderWindow): vec3`, it is now `handleEvent(callData, glRenderWindow): { worldCoords: Nullable<vec3>, worldDirection?: mat3 }`.
  - To upgrade: all instances of `const coords = manipulator.handleEvent(...)` must now be `const { worldCoords } = manipulator.handleEvent(...)`.

## From 26.x to 27

- **abstractimagemapper**: Before this change, the vtkAbstractImageMapper extended vtkAbstractMapper. Now, it extends vtkAbstractMapper3D. Applications with custom sub-classes of vtkAbstractImageMapper that have their own overrides for {set/get}Bounds and {set/get}Center would shadow the superclass methods.

## From 25.x to 26

- **ResliceCursorWidget**: vtkResliceCursorContextRepresentation is deprecated and removed.
Instead, a `vtkSphereHandleRepresentation` is used for `rotation` and `center` handles,
and a `vtkLineHandleRepresenttion` is used for the axes. `rotateLineInView()` now
takes an axis name (string, e.g. 'XinY') instead of a substate. `enableRotation`, `enableTranslation` and `keepOrthogonality` in widgetState are replaced by widget behavior accessors (e.g. `widgetInView.setEnableRotation(false)`). See RCW example.
  - `widgetState.setShowCenter()` is replaced by `widgetState.getCenterHandle.setVisible()`
  - `widgetState.setSphereRadius()` is replaced by `widgetState.getCenterHandle().setScale1()` and `widgetState.getStatesWithLabel('rotation').forEach((handle) => handle.setScale1())`
  - `widgetState.setLineThickness(t)` is replaced by `widgetState.getStatesWithLabel('line').forEach((handle) => handle.setScale3(t,t,t))`
  - `setScaleInPixels()` should now be set on the widget instead of the `widgetInView`.
  - `widgetState.setOpacity()` is replaced by `widgetState.getStatesWithLabel('handles').forEach((handle) => handle.setOpacity())`

This file has been truncated. show original

Javi-r · September 15, 2023, 9:05am

I have already read this document and I can’t find anything related to this.

Sebastien_Jourdain · September 15, 2023, 8:44pm

The From 25.x to 26 has a section on ResliceCursor. Was that not your question?

jadh4v · September 15, 2023, 9:20pm

You should be able to get the origin and normal like this:

    const origin = resliceCursorWidget.getWidgetState().getCenter();
    const planeNormal = resliceCursorWidget.getPlaneNormalFromViewType(xyzToViewType[obj.id]);

And regarding the lineWidget, perhaps you want to do:

lineWidget.getManipulator().setWidgetOrigin(...);
lineWidget.getManipulator().setWidgetNormal(...);