As with my other PR, this is directly available to the polyscope-py library if its dependency to polyscope is bumped :)

Edit: by trying to have "fancy names" for the slicing planes (Slice plane of <structure name>), it ends up being more complicated/stateful with no real benefit. 9f340c1 removes the supplied name to addSlicePlane().

I think this is a good change, I'm happy to merge it. I see some traffic on the PR here, let me know when it is good to go on your end.

Let me ponder on it 'till Friday!

I noticed MSVC does not define the 'and' and 'or' operators unless some compiler flags are enabled [1] (which is why the windows build fails). I have a patch ready for it, I'll send it on Friday if I don't find anything more in the meantime, to avoid restarting a full CI run :)

[1]: https://learn.microsoft.com/en-us/cpp/cpp/keywords-cpp?view=msvc-170 , note (b)

Hey! Sorry to get back to you a bit later than anticipated, things should be good w.r.t. the CI errors from previously.

I added the ability to keep the menu open for interaction with the slice plane menu of a single structure, as I found out while using it that I tended to add multiple slice planes and toggle on/off certain ones regularly. I push the ImGuiItemFlags_AutoClosePopups flag when opening the menu and pop it when going out of the menu. Feel free to accept the PR with or without it :)

Hey @nmwsharp, just a friendly ping to remind this PR is still waiting for a quick review :)

CI passed, only needs your approval on whether you want to keep the menu open, see my last comment for it.