The current behaviour if the user tries to add two components with the same name is that the first one is silently lost, and any references to it in the SIF end up containing IDs of 0, which Elmer isn't very happy with.
This pull request:
Checks to see if a duplicate component already exists, and if so, returns the existing one instead of creating a new one
Raises an exception if there is a name conflict but the data fields are not identical
I was running into this issue with Materials, but I added the check to all components.
The current behaviour if the user tries to add two components with the same name is that the first one is silently lost, and any references to it in the SIF end up containing IDs of
0, which Elmer isn't very happy with.This pull request:
I was running into this issue with
Materials, but I added the check to all components.