View in #cornerstone3d on Slack
@Fancyoung: I have a render problem when I upgrade cornerstone3d (with dicom-image-loader) from 1.8+ to 2.4.0+
The image was load, but can’t be rendered.
It seems stoped on await viewport.setStack(stack)
and can’t goto next step
Hope can get help
@Jurica_Hrg: @Fancyoung I did something that I found on some of the github examples.
define when defining a viewport, I would explicitly define it as a type as Types.IStackViewport
so code would look something like this:
const viewport = renderingEngine.getViewport(viewportId) as Types.IStackViewport
not sure if this is the right angle to tackle this, but seems to be working. This should be resolved if not already resolved.
edit: oh, I misunderstood your concern, you have a render problem. Following this since I’m stuck on the problem.
@Fancyoung: I believe it might be something like createAndCacheDerivedImage
, which returns an IImage
directly in v2, rather than a Promise<IImage>
. However, I have been unable to locate it. I didn’t use createAndCacheDerivedImage
directly.
@Alireza_Sedghi: yes derived image is not async anymore
https://www.cornerstonejs.org/docs/migration-guides/2x/core/#changes-in-createandcachederivedimage-function
@cornerstonejs/core | Cornerstone.js
@Fancyoung: But I didn’t use createAndCacheDerivedImage
. I use await viewport.setStack(stack)
, it seems called loadAndCacheImage
inside. I don’t know which step cause the problem.
@Alireza_Sedghi: hmm
can you create an issue on github with reproducible code?
@Fancyoung: Ok. I created a issue about it: https://github.com/cornerstonejs/cornerstone3D/issues/1664
#1664 [Bug] dicom can’t be rendered when upgrade from 1.8 to 2.4+