Skip to content

connected and disconnected ports hierarchy #130

@websterek

Description

@websterek

Connection and Disconnection signals are emitting variables with source and target port sadly it depends on the "grabbed" port. So if you try to connect the output port of node A to the input port of node B you will have different output than if you grab at first the input port of node B and connect it to the output port of node A... it's confusing so here are some screens.

image

Why it's a problem?
There is no function like "get input nodes" or "get output node" so you can't get the flow of the nodes to create an operation chain.

Solution proposal
Target and source should be always the same (target should be input port and source should be output port).
Or add a function to get connected nodes for input and output ports.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions