AU

> Adding this as a draft to get some feedback on the approach/direction. This would close #311 when completed. Thanks, I will definitely merge this. > Outstanding questions: > >...

It is possible to just use the object material it seems. See: https://dev.opencascade.org/doc/occt-7.1.0/refman/html/class_graphic3d___clip_plane.html#a836e6040401113f600a419edef323831 and https://draw.sview.ru/visualization-clipplane/

> I need to see if I can "break up" the assembly that comes in and add clipping planes to each. I don't understand what you mean here. AFAICT this...

Yes and no. My claim (based on *quickly* inspecting OCCT code) is that this will be solved by using the [SetUseObjectMaterial](https://dev.opencascade.org/doc/refman/html/class_graphic3d___clip_plane.html#a836e6040401113f600a419edef323831) method. Did you try it? Does your experience confirm...

Yes, it looks good enough.

TBH I think this does not fit into the minimalistic scope of CQ-editor. Given that you can use any external editor including ([neo]vim), what is the reason to even consider...

You might want to consider developing a Spyder plugin for CQ/OCP. Then you'll get all the goodies of Spyder. It did cross my mind, but I will not work on...

If you want to simply change the widget to something else, then why not. If it is about something more fundamental (e.g. using the plugin framework), then I'm afraid not...

CQ-editor uses whatever OCCT uses. So you'll need to wait till upstream switches.

Is what you pasted complete? AFAICT in CI conda is not installed, so the issue is quite weird. BTW: nowadays I mostly use mamba.