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

Any output can have multiple connections #21

Closed
megalon opened this issue Dec 5, 2021 · 0 comments · Fixed by #22
Closed

Any output can have multiple connections #21

megalon opened this issue Dec 5, 2021 · 0 comments · Fixed by #22
Assignees
@megalon
Labels
bug Something isn't working

Comments

@megalon
Copy link
Owner

megalon commented Dec 5, 2021

Bug

Any output NodePort can have multiple connections, even though some of them should only be able to have one.

Cause

By default the [Output] attribute's connectionType is set to ConnectionType.Multiple
This should be set to ConnectionType.Override for any output that isn't a List.

Workaround

Currently if two things are connected to a node that is only expecting one, when you export the moveset, the node that was connected FIRST is the one that is exported. The others are ignored.
@megalon megalon added the bug Something isn't working label Dec 5, 2021
@megalon megalon self-assigned this Dec 5, 2021
@megalon megalon mentioned this issue Dec 5, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@megalon megalon

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

v0.3.0 megalon/nasb-moveset-editor
1 participant
@megalon