Parameter must be a Guid or string representing a Guid

Replies to This Discussion

Permalink Reply by Bernhard Mueller on August 15, 2016 at 7:19am

Hi Tom,

Thank's for your answer, but the rs.EvaluateCurve(myLines,0.5) is not working?

any idea how to figure this out.

Attachments:

• guidProblem01.gh, 8 KB

Permalink Reply by Bernhard Mueller on August 17, 2016 at 1:38am

Hi Tom and Anders,

I really thank you for the complete explanation, this is really helpfull.

I have to spend more time to use and understand rc and rs.

Bernhard

Permalink Reply by Anders Holden Deleuran on August 17, 2016 at 3:23am

That's great! I forgot to mention that rhinoscriptsyntax is basically wrapping around RhinoCommon. So a neat way of trying to learn Python modules and how to implement .NET assemblies (i.e. RhinoCommon) in IronPython (i.e. Rhino's Python) is to study the rhinoscriptsyntax module. You can access the source on your harddrive somewhere here-ish:

C:\Users\YOURUSERNAME\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rhinoscript

Permalink Reply by Anders Holden Deleuran on August 15, 2016 at 5:54am

The rhinoscriptsyntax Python module operates on GUID's. The Rhino .NET namespace (i.e. RhinoCommon) operates on RhinoCommon objects. You can right-click the GHPython input parameter to set a typehint which will determine how an object is interpreted by the GHPython component (the default is to pass objects as GUID). I agree with Tom that sticking with RhinoCommon is preferable (there are quite a few threads on this topic if you do a search).