I’m trying to get my head around adding object to a document via python and rhino common and more in general “what scriptcontext is”
In examples I find for instance scriptcontext.doc.Objects.AddSurface(srf)
What I cannot find is a list of the methods available from or accessible from scriptcontext. I have a guess it is the list found at Rhino.DocObjects.Tables.ObjectTable
However it is just a hunch for now. Is there any reading available to explain the paradigm of scriptcontext in relation to Python-Rhino Common?
I’m not the finest expert on the matter, but my amateur interpretation is that scriptcontext is the “bridge” between Python/RhinoCommon and the active document. You use it to access objects that are already in the document as well as add new ones. You can also access and modify any other document related items - tolerances, views, etc. Most of what’s in there can be found in the Rhino.DocObjects Namespace.
To see what subdirectories are under something like scriptcontext.doc, I use a script to write out a text file:
import rhinoscriptsyntax as rs
import scriptcontext as sc
def ExportClassDirectory(direc):
filter = "Text File (*.txt)|*.txt|All Files (*.*)|*.*||"
filename = rs.SaveFileName("Save directory as", filter)
if not filename: return
namext=filename.split("\\")
name=namext[-1].split(".")
file=open(filename,"w")
file.write(name[0]+"\n\n")
for item in direc:
file.write(item+"\n")
file.close()
direc=dir(sc.doc)
ExportClassDirectory(direc)
I guess I should add that I usually use the autocomplete to get where I want to go, my most often used are:
The Active Rhino document (Rhino.RhinoDoc in RhinoCommon) while a script is executing. This variable is set by Rhino before the exection of every script.
doc = None
That is correct when the python script is running in Rhino. If the script is running in Grasshopper, scriptcontext.doc will refer to a temporary document for storing objects created during the execution of the script in a grasshopper component.
Hey Andres,
It’s perhaps more familiar in GH perhaps because everything stays “virtual” until you bake it - like the rest of GH - but you still get a preview. When working directly in Rhino via Python, it’s more abstract maybe, and you do have to get the virtual geometry into the Rhino document at the end. Towards that end the scriptcontext.Add… methods are basically the same as Grasshopper Bake.
I’m actually more comfortable working scripts in Rhino than GH, to me it’s more “direct” and most of my stuff ends up as aliases that run like Rhino commands.
As you see on another thread, I finally resolved the issue for finding the Rhino and System Modules. However, I still can’t get scriptcontext and rhinoscriptsyntax. I made a small script
import sys
print(sys.path)
In many cases things like rhinoscriptsyntax and scriptcontext will not work when executing in a Rhino.Inside CPython environment as there is no user interface and there is no active document to work with.
These libraries are merely there as high level functions on routines in RhinoCommon to make things easier for users.
What are you trying to do? Maybe we can figure out a solution.