NexoNest / Computational geometry / Rhino 8
From a signature
to the geometry.
Understand what the numbers mean, which assumptions matter, and what to check before using a result.
In PyCharm, press Ctrl + Q and click the NexoNest tag, such as #Curve.ClosestPoint. It opens that exact section here. Go beyond the signature with geometric explanations, worked examples, common mistakes, and {{TOPIC_COUNT}} concept lessons. Overloads share one member section.
How to read this reference
Authored lessons explain geometric concepts and pitfalls. Other entries show the API-derived summary and signatures. Coverage is a partial Python view of RhinoCommon; supporting .NET types, null results, collection behavior, and runtime overload selection may need additional handling. Collection outputs use Sequence or Mapping abstractions rather than promising Python lists or dictionaries.
Examples target Rhino 8 Python and use geometry in memory. Stubs do not execute geometry or install Rhino. Model units, tolerances, validity, and success flags remain part of your algorithm's contract.
API summaries originate in RhinoCommon XML documentation. Rhino and RhinoCommon are products of Robert McNeel & Associates. NexoRhino is an independent NexoNest project. See the software terms.
No matching class or method. Clear the filters or try a shorter name.
The geometry behind the API
These NexoNest lessons explain the reasoning behind common modeling operations. Member sections link to the relevant concept without replacing the official API contract.
{{TOPIC_CONTENT}}Further mathematical reading: McNeel · Essential Mathematics for Computational Design.