ms-structural / ms-structural/femdesign-api
Edge connection endpoint behaviour missing from GH
@lorinczandrea is already working on this.
Since Oct 23, 2024.
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Note 1:
This feature exists in the API, but hasn't been implemented in the Grasshopper toolkit yet.
Note 2:
EdgeConnection.JoinedStartPointandEdgeConnection.JoinedEndPointproperties must betrueby default, as they are in FEM-Design.
FEM-Design functionality:
Tasks
- Add new parameters to the existing
EdgeConnectionconstructor or create a new one or add a new method to the class to set the endpoint behaviour attributes.
EdgeConnection.MovingLocal,EdgeConnection.JoinedStartPointandEdgeConnection.JoinedEndPointshould be added to the constructor as input parameters. E.g.:private EdgeConnection(Releases.RigidityDataType3 rigidity, string libraryName = null, bool movingLocal = false, bool joinedStartPoint = true, bool joinedEndPoint = true) { EntityCreated(); MovingLocal = movingLocal; JoinedStartPoint = joinedStartPoint; JoinedEndPoint = joinedEndPoint; if (libraryName is null) this.Rigidity = rigidity; else this.PredefRigidity = new Releases.RigidityDataLibType3(rigidity, libraryName); }
- The
MovingLocalproperty controls the functionality shown in the picture below:
-
Create a new "EndPointBehaviour" GH component.
-
Update existing EdgeConnection GH components (
EdgeConnection.Construct,EdgeConnection.Hinged,EdgeConnection.Rigid). Add "EndPointBehaviour" as an input parameter. -
Update
EdgeConnection.Deconstruct -
Notify the user! Discourse ticket
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.