When trying to build general solutions into clusters and User Objects, I encounter the problem that different types of geometry require different components. I want my User Objects to be as universally applicable as possible.
To avoid unnecessary processing (e.g. breps and surfaces being processed into meshes), I want to filter and dispatch geometry early on. I see I can do that by using the textual description of the geometry and using a filter like ‘Match Text’.
These Geometry descriptions look like this:
Mesh (V: 3 F:1) ← a mesh, obviously
{1.00, 2.00, 0.00} ← a point, or a vector, or a UV coordinate, who knows
Periodic Curve ← a curve
Line (L:5.00 mm) ← a line, and a type of curve, but it doesn’t use that word
Line-like Curve ← basically the same line, but now it does use ‘curve’
Polyline Curve ← a curve, but it would also match with ‘line’
Circle (R:1.00mm) ← a curve, but it doesn’t use that word (also an arc?)
<null>
← nothing, got it
← even more nothing
<empty>
← okay
My question: is there a complete list of the possible descriptions I could encounter?
That would help me write a filter that takes all these cases into account and dispatch the geometry to the right components.