Releases: Kitware/vtk-js
Releases · Kitware/vtk-js
v34.2.0
v34.1.0
v34.0.0
34.0.0 (2025-06-13)
Bug Fixes
- Check if cached opacity texture is deleted (533797c)
- Fix typescript (4a51712)
- Fix update of color and opacity textures (111f193)
- imagereslicemapper: be less sensitive for "snapping" to nearest orthogonal axis (68acd11)
- renderwindowinteractor: observe KeyPress events on RW container instead of document (8cba154), closes #1856
- VolumeMapper: Use the right volume property for texture creation (5f29c73)
Code Refactoring
- move the updatedExtent API to properties (bf98788)
- Move VolumeMapper rendering properties in VolumeProperty (6bc4642)
- OpenGL/Texture: use named parameters (7fbbaa8)
Features
- Add multi property handling to the volume actor (22db7b4)
- Add multi-image support for components to ImageResliceMapper (b5707df)
- KeyboardCameraManipulator: Add typescript (678489c)
- Multi component using volumes (4c9103a)
BREAKING CHANGES
- OpenGL/Texture: the create* methods now use named parameters rather
than positional parameters. - the updatedExtent API has been moved from the mappers
to the vtkImageProperty and vtkVolumeProperty interfaces. vtkImageMapper
does not yet honor the updatedExtent API. - renderwindowinteractor: This may break key press event current behavior.
tabIndex=0 is now added on RW containers. - getTransferFunctionHash becomes getTransferFunctionsHash
It takes a list of functions as argument instead of a single function
Also ImageResliceMapper doesn't wieght color using mix. - the volume mapper fragment shader is very different.
This can cause shader replacements to break.
refactor: Use the right matrices in volume FS shader - Move vtkVolumeMapper's properties related to rendering in vtkVolumeProperty.
Add a clear error message for these widely used methods.
This is part of the MultiVolumeMapper feature.
v34.0.0-beta.2
34.0.0-beta.2 (2025-06-13)
Bug Fixes
Features
- Texture: add support for ImageBitmap texture (5a72ad8)
Performance Improvements
- WebGPU: improve texture upload using ImageBitmap (b2815ae)
v33.3.2
v33.3.1
v33.3.0
v33.2.1
v34.0.0-beta.1
34.0.0-beta.1 (2025-06-05)
Bug Fixes
- Check if cached opacity texture is deleted (533797c)
- Fix typescript (4a51712)
- Fix update of color and opacity textures (111f193)
- imagereslicemapper: be less sensitive for "snapping" to nearest orthogonal axis (68acd11)
- renderwindowinteractor: observe KeyPress events on RW container instead of document (8cba154), closes #1856
- VolumeMapper: Use the right volume property for texture creation (5f29c73)
Code Refactoring
- move the updatedExtent API to properties (bf98788)
- Move VolumeMapper rendering properties in VolumeProperty (6bc4642)
- OpenGL/Texture: use named parameters (7fbbaa8)
Features
- Add multi property handling to the volume actor (22db7b4)
- Add multi-image support for components to ImageResliceMapper (b5707df)
- KeyboardCameraManipulator: Add typescript (678489c)
- Multi component using volumes (4c9103a)
BREAKING CHANGES
- OpenGL/Texture: the create* methods now use named parameters rather
than positional parameters. - the updatedExtent API has been moved from the mappers
to the vtkImageProperty and vtkVolumeProperty interfaces. vtkImageMapper
does not yet honor the updatedExtent API. - renderwindowinteractor: This may break key press event current behavior.
tabIndex=0 is now added on RW containers. - getTransferFunctionHash becomes getTransferFunctionsHash
It takes a list of functions as argument instead of a single function
Also ImageResliceMapper doesn't wieght color using mix. - the volume mapper fragment shader is very different.
This can cause shader replacements to break.
refactor: Use the right matrices in volume FS shader - Move vtkVolumeMapper's properties related to rendering in vtkVolumeProperty.
Add a clear error message for these widely used methods.
This is part of the MultiVolumeMapper feature.