Fix for VTK9 on Mac#16
Conversation
|
Can't test at the moment, but I'll finally be getting a Mac shortly for another project... |
|
I looked at the link and apparently the order is important, In blockbuilder, I created a Another solution would be to create a |
|
If we can get away with not calling |
|
Quoting David Gobbi: "QVTKRenderWindowInteractor.py does not call Start() or Initialize() itself, there’s nothing that can be done there." Reference: https://discourse.vtk.org/t/vtk-9-pyqt-macos-no-rendering/3358/22 If it's working for everyone without |
|
I get a segfault on this branch with the MNE example I usually test with. We could connect to the For now (for us at least) it might be best just to not use VTK9 until they release new wheels with the fix / backport they're doing. |
I'm also having trouble with VTK9 on Linux with the render window refusing to close. Might be best to wait for the next set of wheels. |
Honestly, I have no idea when that could be though... |
|
@larsoner and @akaszynski, what if we hardset |
|
It would be good if platform selectors could be used like in |
|
FYI VTK 9.0.1 is now available on PyPi, but it still renders some garbage for me :( |
Also still having issues with render windows closing on Linux. |
Resolve #15
This works for me locally... someone else should double-check that this is okay (no longer calling initialize at all). Following advice in https://discourse.vtk.org/t/vtk-9-pyqt-macos-no-rendering/3358/14
cc @larsoner and @GuillaumeFavelier