Hi @dale . I had a problem when i used NodeInCode. When i used it in C# SCript, the result return type ( ex : surface). But when i used it in Visual studio ( component Grasshopper ), the result return : IronPython.Runtime.List. I don’t understand. How to convert to Rhino. Please help me. Thanks
Hi @ngthanhlong82,
A screen capture doesn’t really help anyone help you. If you still need assistance, then please post a .GH file.
– Dale
Thanks @dale . I found result.
A number of third party plugins such as OpenNest,GeomGym,ShapeDiver are not found in NondeInCode, while these do meet the requirements as far as I can see.
I also wrote a number of grasshopper components myself. Two components are visible and the other components cannot be used in NondeIncode. All components are in the same gh assembly. I therefore wondered why not all components are visible in NodeInCode, even though they have the correct name?
Hi everyone, and thanks @piac for this!
Apologies for ripping this thread open, but I haven’t found an update to this issue.
Is the quote below still true? I’m trying to use NodeInCode to run a component from a third-party plugin (namely Kiwi3D), and I need to programmatically change its “special settings” as Giulio calls it - I’m calling it “custom component options” as per Rhino - Custom Component Options). Currently I’m using ComponentFunctionInfo.Evaluate
to feed inputs and collect outputs, but I’m puzzled on how to change those special settings.
Thanks in advance, Eduardo
A post was split to a new topic: Access the Rhino.Inside.Revit component “AddGeometryDirectShape”
I just wonder if anyone encounters this:
When I am using a NodeInCode function, sometimes it will suddenly return a NULL result. In this grasshopper canvas, I will not be able to use any NodeInCode function. It will always return Null until I restart my Rhino. Then it works again.
Hi @piac, everyone,
I’d like to utilize the “Contour” component using NodeInCode but I can’t access it because there are multiple components that share the same name. Is there a way around this?
nodeInCodeIssue.gh (11.1 KB)