GUID within python script

Replies to This Discussion

Permalink Reply by Giulio Piacentino on July 25, 2016 at 3:08am

Hi Timothy,

EvaluateCurve returns a Point3d, which is a RhinoCommon point object. It is similar to Vector3d, and it is not a "visible" part of a document, it's just an entity. As such, MoveObject() will not work, because this takes an object in the document, saves the location in the undo stack, and then adds a new object which is translated.

You can however use the rhinoscriptsyntax point methods, like PointAdd() etc, or, if you have a point and a vector, just use the + operator.

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Attachments:

• TanIn.gh, 17 KB

Permalink Reply by Timothy Tai on July 25, 2016 at 8:06am

Hi Giulio,

Thank you for the response.

I have realized that later last night, and did indeed call on the rs.VectorCreate method,

but have followed that with this line of command:

crvCp_vect = rs.VectorCreate(ctr_2, ccx[0])
endPt = rc.Geometry.Point3d.Add(crvCp, crvCp_vect)

instead of the + operator you suggested.

I am guessing using the + operator would be more "efficient"?

And probably better not to mix rc methods in?

Thanks again,

Tim

Permalink Reply by Giulio Piacentino on July 25, 2016 at 8:52am

Hi Timothy,

the + operator is just like calling the Add() static method, it's not particularly more optimized. It's nice because it's shorter, though.

You can mix RhinoCommon and rs methods together, it's fine, as long as you know what you are doing :)

rs.PointAdd(pt, vctr) allows to do the same, using only rhinoscriptsyntax, which is nice.

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Permalink Reply by Timothy Tai on July 25, 2016 at 9:05am

Hi Giulio,

I see, thanks!

I also realized I can do this, too - actually adding the point into the doc through scriptcontext methods and thus get the GUID of the object:

crvCp = rs.EvaluateCurve(cir_min[0], crvCp_par)
crvCp_vect = rs.VectorCreate(ctr_2, ccx[0])
crvCp_GUID = sc.doc.Objects.AddPoint(crvCp)
endPt = rs.MoveObject(crvCp_GUID, crvCp_vect)

And once again, would this be less optimized because it is going through more actions?

Thanks,

Tim

Permalink Reply by Giulio Piacentino on July 26, 2016 at 10:22am

Yes adding it will be slightly less optimized.

Permalink Reply by Timothy Tai on July 26, 2016 at 10:28am

I see, thanks a lot again - am understanding this better now!

Permalink Reply by Kevin MERIC on April 3, 2019 at 1:05pm

Hi Tim,

Did you end up figuring this : "I'd much rather implement something more like a Line SDL component method but I can't seem to figure out how to do that in a rhinoscriptsyntax context)"

I am building a script for an extrusion with a draft angle from any closed curved in any plan that's why I need the Line SDL because it gives me the normal and the distance. Then I can access the end point of the normal and get my extrusion.

This is my first script ever in python and rhinoscript for grasshopper. No coding background, so I am on my own and can't find any solution on forums. I attached the script for you.

Thanks for your help,

Kevin

Attachments:

• extrusion_with_draft_python_any-plane.gh, 7 KB

Permalink Reply by Timothy Tai on April 5, 2019 at 2:11pm

Hi Kevin,

I opened your file but the geometries are not internalized, so I can't really see what you're trying to do. But, from your description, it sounds like you might be able to just use the "Extrude" component in grasshopper where you could just supply your desired vector and length? Also, this forum is obsolete and you recommend you to ask your questions on the McNeel Forum (https://discourse.mcneel.com/).

Tim