-
Notifications
You must be signed in to change notification settings - Fork 19
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
We need Update nodes for elements (frame,shell etc) ! #30
Comments
I'm going to call this a wish for now... As per our discussion today, we are already able to update things like groups and loads and stuff, but [probably] not geometry. We should test and make sure this is the case. And in the future if everyone says they need geometrical update components we can revisit this. |
In my tests today with read and edit sample, I have seen that this is possible. In terms of getting updated from SAP2000, it is about running the 'Read' component again (set boolean to false, then run Dynamo, set it to true, run again). |
@anagpuyol - to confirm... we can update a sap model in dynamo? Read from sap > edit geometry > bake back to sap?? |
To clarify this: we need update nodes to update the geometry of objects read from SAP |
got it. That's what we thought. |
One of the workflows we have discussed beginning of this project: for SAP > Dynamo > SAP I think we need also update nodes to modify structural elements in Dynamo ! we have only Frame.Decompose node so we can watch the properties of each element after we read from SAP but actually we don't to update any of object properties in Dynamo now. I think we need Frame.Update nodes
Scenario one:
input
Frame as Element (read from SAP)
-Line or EndPoints
Scenario Two:
I wish we were able to make some of these input as 'optional' somehow in Dynamo. If this is not happening we might to create individual nodes for each updates such as Frame.Update (for just geometry) get either Line or end Points ) / UpdateSectionprop etc.
Any thoughts on this ? we can also name as 'Modify' !
The text was updated successfully, but these errors were encountered: