Hi @rajaa
Thanks a lot for all the work you’ve put into section tools over the years; the integrated workflow in Rhino 8 is already a big step forward from what we had.
I wanted to ask about API plans (possibly grasshopper components??).
Right now, from what I can tell, we can:
-
Create and manage clipping planes via RhinoCommon (
ClippingPlaneObject,ObjectTable.AddClippingPlane). -
Script Rhino commands from the outside
But we can’t really access the same internal pipeline that the ClippingDrawings command uses:
-
Generate the section curves and hatches tied to a clipping plane.
-
Generate the corresponding “background” linework (silhouettes, visible edges, etc).
-
Control the structured layer output and styles that ClippingDrawings creates.
-
Trigger or hook into the update mechanism in a robust way (auto‑updating when geometry or clipping planes change, without relying on command-calls from Grasshopper).
Current available methods in grasshopper are very slow and low quality.
it would be incredibly useful to have:
-
A set of RhinoCommon methods that expose the core ClippingDrawings operations (input: clipping plane/view, objects; output: section curves, hatches, background curves, organized on layers).
-
A more callback-friendly way to request updates to these drawings when source objects or clipping planes move, instead of calling the UI command.
-
Access to whatever engine you’re using for tangent/hidden/visible line classification so we don’t have to rebuild a parallel Make2D-like stack just to stay in sync with ClippingDrawings.
Do you have any plans to expose more of this in the API in future versions?
Any information about what’s on the roadmap would be really exciting, thinking of possible applications as an architect. Thank you