I'm having innumerable problems with octaviz. Far, far too many to go into detail here.
I have three questions.
1) Is Octaviz compatable with VTK 5? I'm running into errors in the vtk_figure.m file. Namely the functions vtkCubeAxesActor2D.SetProp and vtkRenderer.AddProp are seemingly not defined.
2) Is Octaviz 0.4.0 the stable release?
3) What is wrong with the build system? The system takes half an hour to compile, which wouldn't be so bad, except that when it encounters an error, and cmake produces a great many, everything must be started all over again. It remembers nothing. It's the worst build system I've ever come across. I don't think this project can seriously survive on this cmake system.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As a small note, change the SetProp and AddProp functions above in vtk_figure.m to SetViewProp and AddActor respectively, the 'error: Requested method could not be found.' , error should go away.
I don't know if anything else has changed yet, and I'm trying anything to avoid a rebuild.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
vtk_arrows3.m also requires a change. vtkRenderer.AddProp must be changed to vtkRenderer.AddActor wherever it appears.
PLus vtk_clear.m requires vtkRenderer.GetProps -> vtkRenderer.GetActors and vtkRenderer.RemoveProps->vtkRenderer.RemoveActors.
I'm seeing a pattern here, but since vtk_arrows3 was all I wanted, I'm probably done with this. So I leave it to whomever decides to tackle the next release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately, 0.4.0 is in fact the last official release. We need to make another release soon. You should have better luck with a CVS checkout, which has many new functions and features. With CVS octaviz, I was recently able to compile against vtk-5.0, but I had to comment out
in the file /usr/lib/vtk-5.0/vtkCommonKit.cmake. If you discover how to fix this problem in Octaviz, please let me know.
Cmake is a pain, but is necessary since that is what VTK requires. Unless I do a "cmake clean" it seems to remember what it has already compiled for me, though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm having innumerable problems with octaviz. Far, far too many to go into detail here.
I have three questions.
1) Is Octaviz compatable with VTK 5? I'm running into errors in the vtk_figure.m file. Namely the functions vtkCubeAxesActor2D.SetProp and vtkRenderer.AddProp are seemingly not defined.
2) Is Octaviz 0.4.0 the stable release?
3) What is wrong with the build system? The system takes half an hour to compile, which wouldn't be so bad, except that when it encounters an error, and cmake produces a great many, everything must be started all over again. It remembers nothing. It's the worst build system I've ever come across. I don't think this project can seriously survive on this cmake system.
As a small note, change the SetProp and AddProp functions above in vtk_figure.m to SetViewProp and AddActor respectively, the 'error: Requested method could not be found.' , error should go away.
I don't know if anything else has changed yet, and I'm trying anything to avoid a rebuild.
vtk_arrows3.m also requires a change. vtkRenderer.AddProp must be changed to vtkRenderer.AddActor wherever it appears.
PLus vtk_clear.m requires vtkRenderer.GetProps -> vtkRenderer.GetActors and vtkRenderer.RemoveProps->vtkRenderer.RemoveActors.
I'm seeing a pattern here, but since vtk_arrows3 was all I wanted, I'm probably done with this. So I leave it to whomever decides to tackle the next release.
Unfortunately, 0.4.0 is in fact the last official release. We need to make another release soon. You should have better luck with a CVS checkout, which has many new functions and features. With CVS octaviz, I was recently able to compile against vtk-5.0, but I had to comment out
"vtkSignedCharArray"
"vtkLongLongArray"
"vtkUnsignedLongLongArray"
in the file /usr/lib/vtk-5.0/vtkCommonKit.cmake. If you discover how to fix this problem in Octaviz, please let me know.
Cmake is a pain, but is necessary since that is what VTK requires. Unless I do a "cmake clean" it seems to remember what it has already compiled for me, though.