MatthewFlamm

Since this is labelled as 'good first issue' and to avoid churn with new contributors, I will be explicit in my agreement that we should not create a new filter...

We might also find problems with differing vtk versions... Is it still significantly faster to build the documentation without the interactive plots? We could consider doing this for the older...

Defined here. https://github.com/pyvista/pyvista/blob/895475d9255e07e6c3e92e9d647706a349fd5fed/pyvista/core/dataobject.py#L430 Might need to be `NumpyArray[Any]`, but not sure here.

> ❓ Also, is there a specific reason why `pyvista` isn't using `dependabot` to automatically update the `github-actions` package ecosystem? I don't know a reason not to do this, but...

> Is that what the `--fail_extra_image_cache` flag is used for with https://github.com/pyvista/pytest-pyvista? > > Maybe this flag just needs to be added to CI This should be correct.

You are right, my memory is bad. https://github.com/pyvista/pytest-pyvista/issues/28

I think it is likely that this issue and #7298 are a change in default tick location logic in vtk combined with a perspective bias in viewpoint.

I do not think my previous message is correct now. This is clear minimal reproducible evidence that there is some bug. I agree with this suggestion in trying to figure...

I agree with you that it seems like the tick placement doesn't match the labeling logic. The proposed workaround assumes that the tick placement always works like this. It would...

In my reading of the vtk example, the strategy is to produce a screenshot and then use the screenshot image as a mesh to do the external contouring. This is...