Question about the limitations of “IExternalImplementedNode” nodes

FlowCanvas Forums Support Question about the limitations of “IExternalImplementedNode” nodes

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #3596


    Is it normal that only 1 instance of an “IExternalImplementedNode” (EIN) node works at a time and only the first node you created this way?
    For example, I have a Monobehaviour that implements this EIN interface and let’s say this gets added to a GameObject in the scene, next I add this component as an implemented node to a FlowScript in the same scene. Now when I add this implemented node to a second FlowScript in again the same scene the outgoing Flow on this second implemented node instance does not trigger or does not get called.

    Just wanted to know if this is by design? or a bug? or maybe I’m missing something here?
    if it is by design, does anyone know if it would be possible for us to make a change such that this would be allowed?
    Any help would be greatly appreciated!

    Kind regards,




    Quick update, in case this might help someone.

    I found a solution to our problem, after doing some debugging I discovered that we were overwriting the single output flow field we had in the monobehaviour class, changing this to a list and adding all the incoming outputflows to this list fixed it.
    So instead of referencing one outputflow and call it we track all incoming ones, from the RegisterPorts method, and als call all of them in a foreach loop.

    All good!

    Quick example on the solution…

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.