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
Hey, we use DCMjs to create structured reports from cornerstone and cornerstone-tools (not the new cornerstone3d).
For the most part this seems to work just fine, but we recently wanted to add FreehandRoi tooling to the reports. This never seemed to work as tool was always undefined when saving the report. Upon further examination the code seems to work just fine if tool is put into the argument list.
The question is really just, why is tool commented out? The function seems to work just fine with it in, and not work at all without it.
The text was updated successfully, but these errors were encountered:
@SveinungOverland - I'm not sure why it was commented out - it shouldn't have been, but for that class I was just updating it to match the format of the other ones, without having a full configuration that enabled it to run. Please create a PR with it added back end, testing both save and restore.
@wayfarer3130 - I created the PR, but from what I can see dcmjs seems to be missing a testing structure for adapters and I don't think I should be the one to create it. So if you know of anyone more familiar with dcmjs and js testing I would appreciate if you tag them here.
dcmjs/src/adapters/Cornerstone/FreehandRoi.js
Lines 46 to 47 in 7852832
Hey, we use DCMjs to create structured reports from cornerstone and cornerstone-tools (not the new cornerstone3d).
For the most part this seems to work just fine, but we recently wanted to add FreehandRoi tooling to the reports. This never seemed to work as tool was always undefined when saving the report. Upon further examination the code seems to work just fine if
tool
is put into the argument list.The question is really just, why is
tool
commented out? The function seems to work just fine with it in, and not work at all without it.The text was updated successfully, but these errors were encountered: