Refactor Motions.Rigid - Githubissues

strusoft / femdesign-api

FEM-Design API

https://femdesign-api-docs.onstrusoft.com/

Apache License 2.0

41 stars 20 forks source link

Open Marco-Pellegrino opened 2 years ago

Marco-Pellegrino commented 2 years ago

Consider removing Motions.RigidPoint and Motions.RigidLine and use only Motions.Rigid.

andosca commented 2 years ago

The stiffness of the two are different.

Marco-Pellegrino commented 2 years ago

True! it might be worth implementing the logic to assign the "rigid value" and remove what it is not necessary.

I have just notice that the user might mistakenly assign a RigidLineValue to a PointSupport and the component does not raise any error.

andosca commented 2 years ago

Good point. It might be difficult to figure out which motions / rotations to use.