-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to latest vtk-js in dicom_viewer #1951
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+2
I might have been too fast... Since it was bulding correctly I forgot to verify the plugin dicom_viewer was correctly working with the latest vtk-js version. It appears that it's not the case: v2.13.4 works fine, should we merge immediately a commit with this lower version the time we fix the issue? |
Hm, is this a regression in vtk-js? We may want to open a bug against vtk.js -- I think they use semver, so breakage is not expected here, unless we are depending on undefined behavior. |
2.13.5 is Rendering: support intermixing of surfaces and volumes Maybe the ImageMapper that you did don't play nice with it and since there is no test on that mapper we did not notice it? |
@jourdain I'm getting a warning message in the console that says "empty event loop", does that indicate a problem? |
Also when dragging the mouse:
|
The missing image is a regression. We have an example for the class but not a test. I'll add one tomorrow. For now this MR should fix the issue. Kitware/vtk-js#212 |
I don't think so. Although the interaction has also been updated to use the requestAnimationFrame which could be the source of the issue here. |
@jourdain Should I create a vtk-js or a girder issue for this dragging error then? |
The code seems to be in vtk.js |
As discussed in the MR girder#1951 , vtk-js faces a regression issue: Kitware/vtk-js#214 This downgrade would be revert at the time the issue will be fixed
Should be fixed now in master via Kitware/vtk-js#215 |
@martinken Is there a tag to the latest vtk-js version (including your modifications)? I would like to give a try but the |
I gave a try with v2.18.3 and unfortunately we still have issues:
The dragging mouse seems to work but the image is still missing. |
You can, we may need an example for the issue. The example we have https://kitware.github.io/vtk-js/examples/ImageMapper.html doesn't seem to show that issue. |
I believe I know what the issue is, just may not show up on every platform. I'll try to get in a fix this morning. |
All right, let me know if you need anything! Thanks a lot |
give 2.18.4 a shot |
Can you try |
@martinken FWIW, 2.18.4 fixed both bugs for me |
Thanks, I think what Mayeul is seeing is hardware specific. I think I have a fix ready though that shoudl solve the issue for those that see it. |
I tried to use your commit by modifying
During
Is your commit correctly used by doing this? If yes, this commit solved the issue! |
If you do |
0.0.0-semantically-release |
Ah, that makes sense, I think they use a tool that changes that value automatically at release time. |
You can try |
I get
|
I merged the change, so the system should produce a new version soon. |
Okay, I just checked out the file if it was correctly modified according to Kitware/vtk-js@568abd0 after modifying So, @martinken, we are good to merge Kitware/vtk-js#217 , it fixed the issue! Thank you very much for your help guys :) |
2.18.5 |
Awesome, glad to hear it! Thanks for testing it out. |
girder#1951 introduced issues: - dragging mouse over image broken (fixed by Kitware/vtk-js#215) - missing image (fixed by Kitware/vtk-js#217)
This supersedes #1950