We noticed a lot of calls to the vtkCubeAxesActor were slowing down our app when we tried to update (add and remove) many GeometryRepresentations at the same time.
This change should make sure CubeAxes is never initialized or called if showCubeAxes is not true.
We noticed a lot of calls to the vtkCubeAxesActor were slowing down our app when we tried to update (add and remove) many GeometryRepresentations at the same time.
This change should make sure CubeAxes is never initialized or called if
showCubeAxes
is nottrue
.