[Simulation] Trigger error when Node already contains component #5212
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some component types (see list below), visitors only consider the last added component in the Node. This is due to the fact that Node stores some links as
SingleLink
. The user has no idea of that, so this PR triggers an error when a second component of the same type is added into a Node.The error message looks like:
Note that the name is 'unnamed' because its has not been parsed. I added the address of the object in case both objects have the same name.
A unit test is added on
BaseMechanicalState
.List of concerned components:
By submitting this pull request, I acknowledge that
I have read, understand, and agree SOFA Developer Certificate of Origin (DCO).
Reviewers will merge this pull-request only if