Draft: support vtk files generated from Gmsh #1547
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes issue #1544
Possibly related to GenevieveBuckley/napari-meshio#4 ?
I had a go at addressing issue #1544. I am confident that commit 8c42f167ea2379570bce046548c1ddbcba2bcee0 is correct, but I am not confident about the rest, and whether the overall result is correct.
Details
I used the example file suggested in issue #1544:
This mesh can be displayed in Paraview:

When you checkout this PR branch:
and read in the example Gmsh .vtk file:
You get this summary output:
So everything seems to work ok so far, although I am not sure if this is the expected output.
To confirm whether it's working correctly, I would really like to load the mesh from meshio, into a visualization program to look at it. Then we could see if it looks like the original input or not.