Nicholas Sharp

For now I'll remove the ImGUI change so I can merge this PR with the other two.

Hmmmm, note the build failures from the CI. I think to use `STB_IMAGE_STATIC` we'd need to also switch to including the implementation in every file which uses it, right? ```...

This is awesome!! Thanks as always for the contribution! Sorry for not saying anything sooner, I went down a rabbit hole of checking out the pre-existing community ImGui bindings generators....

I looked into that one as well (along with the cimgui & litgen projects linked above). I'm a little wary of depending on an external project that could be abandoned,...

Oh actually I lied, it looks like the `cimgui` .json does indeed have the original function name as a field. We'd have to do some translating, but I think it...

Any updated thoughts on this? I'm looking to release a new version soon and it would be a good time to update these bindings. I spent a little while looking...

By the way I'm also looking to include bindings [ImPlot](https://github.com/epezent/implot). I suppose it should be easy to generate bindings for that too with a similar setup?

Short answer: no, unfortunately. Polyscope builds it's own bindings for ImGui etc, and due to the way Python libraries work you cannot trivially intermix copies of libraries compiled as separate...

Right now it's really just a list of hexes and a list of tets, no support for other types / transitional elements, etc. My knowledge of volume meshes is pretty...

This is interesting, I'm not sure quite what's causing it, it would be good to fix. As you say, antialiasing is one possible cause, it is controlled explicitly with `ps.set_SSAA_factor(2)`...