I’ve got what I need using RhinoCommon. I guess I’m just curious if I can do this with RhinoScript. I’m left with a boundary I can’t delete because it’s a rhino object. Now… how hard is it to deal with? It’s not… I need to learn a bit more… but if I can do it all in RhinoScript and leave the RhinoCommon out there’ll be more advantages down the line.
AI’d my way through this but it wasn’t pretty and I’m not proud of it. I guess if I had to summarize this small hurdle it would be this: I can figure out how to get the object ID from a Rhino Object or more specifically a Curve.
https://developer.rhino3d.com/api/rhinocommon/rhino.geometry.curve
I realized I got the object ID when the curve was created and I was able to work with that.
RhinoCommon > RhinoScript.
Not sure why you think doing it in RhinoScript there’ll be more advantages. It is the other way around.
Rhinoscript has excellent documentation and overall I think it’s a really good system with good syntax when adapted to Python. It’s actually a big reason I learnt Python. People more often than not share scripts and give out advice/solutions that includes rhinoscriptsyntax.
RhinoCommon might be good. I myself have struggled with it. It seems like it could be an excellent API but is missing some of the functionality and convenience compared to other API’s. The documentation is often unclear or non-existent. I think you guys are working on that of course, but for now it’s not enough for someone like me. You guys are helpful but also busy so when I do hit a wall it’s sometimes game over. At least with Rhinoscript there’s so many examples you can almost always find the solution. And the AI is likely drawing from all of that as well.
The pace at which I code if I try and use RhinoCommon is over 10x slower than say, AutoLISP or even .NET for AutoCAD. And now that I’ve finally learnt Python I’m getting up to that productivity level with Python. It might seem like I’ve been asking lots of questions lately but the questions to line-of-code ratio is vastly improving.
I think for me using Rhinoscriptsyntax first and only diving into RhinoCommon for things like above is the way to go. I’m just building a collection of small and relatively simple tools.