STYLE: avoid VTK InsertNextPoint if we already know the sizes
- avoids potentially issues if we reusing a vtkPoints array, and should be marginally faster without the additional range checking.
Showing
- applications/utilities/postProcessing/graphics/PVReaders/PVFoamReader/vtkPVFoam/vtkPVFoam.H 1 addition, 1 deletion...ing/graphics/PVReaders/PVFoamReader/vtkPVFoam/vtkPVFoam.H
- applications/utilities/postProcessing/graphics/PVReaders/PVFoamReader/vtkPVFoam/vtkPVFoamFieldTemplates.C 18 additions, 22 deletions...VReaders/PVFoamReader/vtkPVFoam/vtkPVFoamFieldTemplates.C
- applications/utilities/postProcessing/graphics/PVReaders/PVFoamReader/vtkPVFoam/vtkPVFoamMesh.C 16 additions, 8 deletions...graphics/PVReaders/PVFoamReader/vtkPVFoam/vtkPVFoamMesh.C
- applications/utilities/postProcessing/graphics/PVReaders/PVFoamReader/vtkPVFoam/vtkPVFoamMeshLagrangian.C 6 additions, 5 deletions...VReaders/PVFoamReader/vtkPVFoam/vtkPVFoamMeshLagrangian.C
- applications/utilities/postProcessing/graphics/PVReaders/PVFoamReader/vtkPVFoam/vtkPVFoamTemplates.C 13 additions, 4 deletions...ics/PVReaders/PVFoamReader/vtkPVFoam/vtkPVFoamTemplates.C
- applications/utilities/postProcessing/graphics/PVReaders/PVblockMeshReader/vtkPVblockMesh/vtkPVblockMeshConvert.C 33 additions, 70 deletions.../PVblockMeshReader/vtkPVblockMesh/vtkPVblockMeshConvert.C
Please register or sign in to comment