Hi. Users are telling me that they cannot finish surgical planning because they cannot make boolean operations because the CombineModels module is not found, because the extension manager cannot install Sandbox extension because it is not available (it is one of the dependencies of BoneReconstructionPlanner)
If you search ‘Sandbox’ in the extension manager in the Stable release it doesn’t find it. If you search ‘Sandbox’ in the extension manager in the Preview release it finds it but the new webpage does not load, it just freezes.
@lassoan, @jcfr, @Sam_Horvath could you help?
Is there any chance the CombineModels module gets to be part of Slicer Core?
From today’s Slicer stable build results of SlicerSandbox it appears CombineModels is breaking the build likely because it was made compatible with VTK9 and Slicer stable 4.11.20210226 is using VTK8. It’s unclear as a “SandBox” extension if compatibility with latest stable is attempted, or only with latest Preview code.
Yeah that is weird and I see it too. The link is below and the page doesn’t load the correct contents. I haven’t found yet another extension page that has this issue. Clicking the install button from Extensions Manager search results does work for it, but you can’t view the webpage for the extension.
I haven’t thought of making Combine Models module compatible with VTK8. @mau_igna_06 has Combine Models ever worked in Slicer-4.11? If not, then we should just disable the Combine Models module for Slicer-4.11 (I don’t think anybody would want to spend time with debugging VTK8-related build errors on Windows, Linux, and Mac).
I never click on the extension’s page because that install button there does not work. You can click on the install button directly on the extension listing instead.
@lassoan I could revert the combineModels changes in a new branch and change the extensios index file of the stable release to point to that branch. What do you think?
Yes, you can create a 4.11 branch for the Sandbox extension and make changes that fix the VTK8 build errors. However, considering that we hope to replace Slicer-4.11 in a couple of weeks, I’m not sure if it is worth the effort.