Curves and Surfaces baked automatically?

Scripting
1

Hello
When i use rs.Add… everything baked and added to Rhino , how to solve that?

helix.gh (8.6 KB)

image
image1234×555 70.1 KB

2

I try with disable redraw an convert curve to Rhino geometry but always the same problem !

image
image1416×705 174 KB

3

switch back to grasshopper document before you call the “add” methods
try something like sc.doc = ghdoc

1 Like
4

Thank you work fine, i will test it with hatch

5

Sadly when compile to ghpy component there is a problem with ghdoc and ghenv
I choose rhino geo to create the spiral

6

in the python dev mode you can switch back and forth with the following
image
I did these in the beginning:
import Rhino as rh
import scriptcontext as sc
in case you wonder what those are

1 Like
7

Thanks i will try this

Yes i know :slight_smile:
image

8

Don’t work and this error appears

image
image1338×507 84.4 KB

image
image893×526 35 KB

9

I don’t know what you are running though. What are you doing with the x, y and z?
That is a generic error when you have variables point to things non-existing.

10

X,Y,Z have no relation with this, ghdoc and RhinoDoc works fine, if you print ghdoc and GhPython.DocR…
You can see that they are not the same.
Did you try it and worked for you?

X is curve
Y is point
Z is float

11

What I meant was there might be something else in your code that’s causing the error. I couldn’t see how you are calling those variables. Please post a snippet.

if you just need to make a component that creates spirals you can do this without all the doc switching

class Spiral(component):
    def RunScript(self, P, D, S, T,R0, R1):
        if not P: P = (0,0,0)
        if not D: D = (0,0,1)
        if not S: S = 1
        if not T: T = 1
        if not R0: R0 = 1
        if not R1: R1 = 1
        c = rs.AddSpiral(P,D,S,T,R0,R1)
        return c

image

make sure you are in the SDK dev mode
image

12

As i posted before i find another way because rs.Add… always bake curves or solids … if sc.doc used in any different script even if it is compiled to ghpy.
But if i find another solutions this will be always good
and the code is very simple

test.gh (6.4 KB)

image
image1508×512 141 KB

13

I don’t quite follow.
In general, yes, you’d want to be careful changing the scope of the script. Whenever you do sc.doc= it should be flagged as a potential “loose end”.
Better suggestion is to use RhinoCommon directly
For example rs.OffsetCurve has its equivalent here


In this case you do need to run rs.coercecurve because the method is called from a Curve object
1 Like
14

Thanks , yes that what i did and if ghenv and ghdoc can compiled this will be better