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.

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

Node Inputs Enhancement #177

Open
HeftyCoder opened this issue Dec 6, 2023 · 0 comments
Open

Node Inputs Enhancement #177

HeftyCoder opened this issue Dec 6, 2023 · 0 comments

Comments

@HeftyCoder
Copy link
Contributor

Node Inputs are only allowed one connection. I'd argue that one should be able to define how many connections are allowed for a Node Input, i.e negative number for infinite and a positive number for constrained, which can be defaulted to 1.

I did notice that in ryvencore the graph_adj_rev relates one input to a single output, which means this implementation is ryvencore specific as well. I could look into the refactoring needed for this to work, but first I want to know:

  • Is there a reason that an input takes only one output? Would data be lost otherwise? I can see how the design of connecting and the nodes updating on connection would favor ryven, but it probably limits ryvencore.
  • Is this tightly coupled with the whole system, or could it be easy to change? I don't have a lot of time to spend on this, so an estimation on how much things might break will help me.

I hope I am right in saying that an input updating from a number of outputs can make sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant