Passing objects as class properties to another GHPython component

Replies to This Discussion

Permalink Reply by Anders Holden Deleuran on August 21, 2013 at 5:25am

When using rhinoscriptsyntax functions you usually have to use Guids. You can set this manually by assigning type hints to your input parameters on the GHPython component like so: 

Right-click the input parameter -> Type Hint -> Select the one called "ghdoc object".

Permalink Reply by Daniel da Rocha on August 21, 2013 at 6:03am

Hello Anders!

Thanks for the quick reply... I am using Guids... I have a list of cones as GUIDs. When I say:

>> print cones

[<System.Guid object at 0x00000000000006DD [7faf5bf4-37f7-4a4d-8c96-e50ba89d07c9]>, <System.Guid object at 0x00000000000006DE [7ae3e35f-02bf-42f6-a74c-c5087c1e578b]>, <System.Guid object at 0x00000000000006DF [07e8e363-56a1-476d-954f-96dfe227db91]>]

I get the right results... but when I do then

>>print cones[0]

7faf5bf4-37f7-4a4d-8c96-e50ba89d07c9

I get only this number. Which is exactly the number that is not being accepted by my next rhinoscriptsyntax commands...

What am I doing wrong??

Daniel

Permalink Reply by Anders Holden Deleuran on August 21, 2013 at 6:27am

Hmm, that's a good question. I pretty much stick to straight up RhinoCommon at this point. Especially within GH Python components, which means that I never really have to deal with GUIDs unless if I'm referencing objects in the Rhino document directly in the code. Could you upload a file demonstrating this behaviour perhaps?

Permalink Reply by Daniel da Rocha on August 21, 2013 at 6:42am

Hi Anders,

Attached is the file with those 3 definitions.

It is still a very rough sketch (don't mind the weird code!)

Most important is:

• 01 created my "cone towers"
  • Line 62 is where I actually create the cones as a rs.AddCone command; would you use here Rhino.Geometry.Cone instead?
• 02 is a simple output of parameters
  • here you see how the cone geometry is displayed with no problems when I get them from the tower.cones property
• 03 is where i have trouble
  • Line 26-30 this does not work! It does not accept my Guids for anything
  • Line 41-42 shows how the guid is actually valid when I try to output one cones, for example

So you'd rather use commands from RhinoCommons instead of rhinoscriptsyntax to manipulate and create geometry?

Thanks !!!

Daniel

Attachments:

• 130821-cones.gh, 15 KB

Permalink Reply by Marios Tsiliakos on August 21, 2013 at 6:28am

Hello,

I suppose you don't feed the print  output to the next python component, hence you are not trying to convert strings into guid or geometry or whatever.

if you manipulate the cones in the first component then the output is not guids anymore but IGH_goo geometry, so its not a guid and as a result cannot be handled by rhinoscript commands.

on the other hand it would help to preview some of the code.

M.

edit: +1 to Anders ''stick to straight up RhinoCommon'' 

Permalink Reply by Daniel da Rocha on August 21, 2013 at 6:44am

 +1 to Anders ''stick to straight up RhinoCommon'' 

This is actually interesting, because I was actually confused as to when should I use rhinoscriptsyntax or RhinoCommon ... I'll try it out with RhinoCommon and see where I get to....

Permalink Reply by Daniel da Rocha on August 21, 2013 at 6:46am

This actually makes my life a thousand times easier........

Permalink Reply by Anders Holden Deleuran on August 22, 2013 at 2:26am

Not just easier, often times faster. Glad you got it working :)

Permalink Reply by Daniel da Rocha on August 21, 2013 at 8:18am

Quick update... All works now. I followed the advice to use RhinoCommon and got rid of GUIDs altogether.