-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document.current always null #3166
Comments
@epeter- Not seeing it in the current daily build. |
actually the doc is forwarded to the custom node's python code. import clr Import DocumentManagerclr.AddReference("RevitServices") Import RevitAPIclr.AddReference("RevitAPI") Import ToDSType(bool) extension methodclr.AddReference("RevitNodes") #The inputs to this node will be stored as a list in the IN variable. #Assign your output to the OUT variable |
Actually i used that workflow in 7.xxx
Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. |
the document.current node always results in null.
daily build 7.4.3192
used as input in "ID to Elements" and "id to Elements"
worked in earlier releases
The text was updated successfully, but these errors were encountered: