BUG: polyMesh constructor AUTO_WRITE flag, ignored readOpt (#1147)

- fixed some more places with an explicit AUTO_WRITE.

BUG: revert handling of the readOption. It should not be NO_READ.

  In cases where the user a IOobject without specifying read/write, it
  defaults to NO_READ anyhow. However, the move constructor can also
  be called with empty lists and a read option. This has the same
  signature, but obviously will not work with NO_READ.
This commit is contained in:
Mark Olesen
2019-01-07 22:23:19 +01:00
parent 620f5274d0
commit 74d9dc3f50
9 changed files with 35 additions and 21 deletions

View File

@ -213,7 +213,9 @@ int main(int argc, char *argv[])
(
fvMesh::defaultRegion,
runTime.timeName(),
runTime
runTime,
IOobject::NO_READ,
IOobject::AUTO_WRITE
),
pointField(mesh.points()), // Could we safely re-use the data?
faceList(mesh.faces()),