You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is the same bug as #669 but I thought I'd provide a little more information. After adding a provider (for eg. hardcodedMetaDataProvider), StackViewport.setStack never queries the list of metadata providers. If I put a console.log at this line of hardcodedMetaDataProvider.ts, it never appears.
Steps to Reproduce
It's easily viewable on the current WebLoader demo.
View console, and notice that the image hasn't loaded
The current behavior
Initialize CornerstoneCore
Add a meta data provider with CornerstoneCore.metaData.addProvider(HardcodedMetaDataProvider, 1)
Register image loader, initialize renderingEngine and viewport
Attempt to load an image with stackViewport.setStack(url)
Step 4 fails to load the image, because the metadata is undefined
The expected behavior
The last version this works on is version 0.47.0 of the @cornerstonejs/core . If I downgrade to that version, it loads as expected. As soon as it's upgraded to 1.1.0 it breaks.
OS
Windows 10
Node version
20.3.1 (Current)
Browser
Chrome 114.0.5735.134
The text was updated successfully, but these errors were encountered:
Describe the Bug
I believe this is the same bug as #669 but I thought I'd provide a little more information. After adding a
provider
(for eg. hardcodedMetaDataProvider),StackViewport.setStack
never queries the list of metadata providers. If I put aconsole.log
at this line ofhardcodedMetaDataProvider.ts
, it never appears.Steps to Reproduce
It's easily viewable on the current
WebLoader
demo.The current behavior
stackViewport.setStack(url)
The expected behavior
The last version this works on is version
0.47.0
of the@cornerstonejs/core
. If I downgrade to that version, it loads as expected. As soon as it's upgraded to1.1.0
it breaks.OS
Windows 10
Node version
20.3.1 (Current)
Browser
Chrome 114.0.5735.134
The text was updated successfully, but these errors were encountered: