ENH: provide xfer methods for the meshed surface components.
- the surfMesh classes where originally designed with limited (protected) access to the underlying components. This is to avoid unintentional direct changes, since these can quickly lead to inconsistencies with the topology addressing etc. However, if we wish to efficiently adjust surfaces, it is useful to modify the components directly. The compromise is to provide 'xfer' methods: - xferFaces() - xferPoints() - xferZones() These transfer the contents to an Xfer container for reuse, while also resetting the topology addressing. To apply the changes, the reset() method is used.
Showing
- src/surfMesh/MeshedSurface/MeshedSurface.C 47 additions, 7 deletionssrc/surfMesh/MeshedSurface/MeshedSurface.C
- src/surfMesh/MeshedSurface/MeshedSurface.H 15 additions, 0 deletionssrc/surfMesh/MeshedSurface/MeshedSurface.H
- src/surfMesh/MeshedSurfaceAllocator/MeshedSurfaceIOAllocator.H 1 addition, 1 deletion...urfMesh/MeshedSurfaceAllocator/MeshedSurfaceIOAllocator.H
- src/surfMesh/UnsortedMeshedSurface/UnsortedMeshedSurface.C 8 additions, 0 deletionssrc/surfMesh/UnsortedMeshedSurface/UnsortedMeshedSurface.C
- src/surfMesh/UnsortedMeshedSurface/UnsortedMeshedSurface.H 3 additions, 0 deletionssrc/surfMesh/UnsortedMeshedSurface/UnsortedMeshedSurface.H
- src/surfMesh/surfMesh/surfMesh.C 23 additions, 1 deletionsrc/surfMesh/surfMesh/surfMesh.C
- src/surfMesh/surfMesh/surfMesh.H 9 additions, 0 deletionssrc/surfMesh/surfMesh/surfMesh.H
- src/triSurface/triSurface/interfaces/VTK/readVTK.C 1 addition, 1 deletionsrc/triSurface/triSurface/interfaces/VTK/readVTK.C
- src/triSurface/triSurface/triSurface.H 3 additions, 3 deletionssrc/triSurface/triSurface/triSurface.H
Please register or sign in to comment