stackPrefetch stops when selecting different element
See original GitHub issueHi, I have two divs. I assign a stack to each and do a cornerstoneTools.stackPrefetch.enable(elem1);
to start prefetching the 1nst div. Then, I do the same on the 2nd div (I call it elem2). The problem I found is the prefetching of the first element stops when the 2nd element is enabled.
Is this the expected behavior of stackPrefetch?.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Prefetching multiple stacks stops prematurely - Google Groups
When stackPrefetch is enabled on an element, it adds all the stack's imageIds to the requestPoolManager. That will request images in parallel, up...
Read more >Stop selection of element on background double-click
I have a problem that when the background is double-clicked the first element is selected. Check out this fiddle: https://jsfiddle.net/cb6fjr7n/1/.
Read more >Stack Tools
A stack can include all images in a series or a subset of them. A stack can even include images from different series...
Read more >cornerstone-tools - UNPKG
stackTools/stackPrefetch.js","webpack://cornerstoneTools/. ... updateImage(element);\n}\n\n/**\n * Stop the CornerstoneToolsTouchStart event from\n ...
Read more >Design specification - SIMH
At IID, the I Box selects a microcode address to drive to the Microsequencer. ... In the third case, a different case target...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Looks like we can close this since #542 was merged. Thanks!
We’ve add the same problem and solved it by tweaking the stack prefetch:
We’ve tested it with two side-by-side viewer and it worked like a charm: each time we interact with a viewer, the other one stops loading and the current one resumes loading, even if the current image changes. When it’s over, the remaining one loads. Really neat!
I’m working on a PR to handle it with a configuration parameter.