Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove rules to force only one instance of a certain component in a node #5217

Open
bakpaul opened this issue Jan 15, 2025 · 0 comments
Open

Remove rules to force only one instance of a certain component in a node #5217

bakpaul opened this issue Jan 15, 2025 · 0 comments
Labels
issue: bug (minor) Bug affecting only some users or with no major impact on the framework issue: discussion Open topic of discussion STC#19 Simple tasks for STC#19 coding sprint

Comments

@bakpaul
Copy link
Contributor

bakpaul commented Jan 15, 2025

This issue is resulting for this PR : #5212

The mechanism of having only one instance of a component comes from the fact tthat hidden mechanism in SOFA automatically detect links based on those rules : e.g. mappings automatically detect input and outpu mstate. But is this really what we want ?

If we force links to be explicited then nodes have no more utility except sorting components.
@bakpaul bakpaul added issue: discussion Open topic of discussion issue: bug (minor) Bug affecting only some users or with no major impact on the framework STC#19 Simple tasks for STC#19 coding sprint labels Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
issue: bug (minor) Bug affecting only some users or with no major impact on the framework issue: discussion Open topic of discussion STC#19 Simple tasks for STC#19 coding sprint
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bakpaul