Updates to polyMesh::changing_ flag

It's better to update it in polyTopoChanger::changeMesh() than in
polyMesh::updateMesh(). This way, it is consistent with directTopoChange engine
This commit is contained in:
Vuko Vukcevic 2018-04-25 10:00:27 +02:00
parent 8a14f3ce8e
commit 047bc41b27
2 changed files with 6 additions and 3 deletions

View file

@ -2491,6 +2491,9 @@ Foam::autoPtr<Foam::mapPolyMesh> Foam::polyTopoChanger::changeMesh()
// Increment the morph index
morphIndex_++;
// Mark the mesh as changing
mesh_.changing(true);
return topoChangeMap;
}
else
@ -2504,6 +2507,9 @@ Foam::autoPtr<Foam::mapPolyMesh> Foam::polyTopoChanger::changeMesh()
// Sync mesh update
mesh_.syncUpdateMesh();
// Mark the mesh as changing
mesh_.changing(true);
}
return autoPtr<mapPolyMesh>(new mapPolyMesh(mesh_));

View file

@ -36,9 +36,6 @@ Description
void Foam::polyMesh::updateMesh(const mapPolyMesh& mpm)
{
// Mesh is changing
changing(true);
// Update zones. Since boundary depends on zones, they need to be
// updated first. HJ, 20/May/2014
pointZones_.updateMesh();