Non-Reentrant Actors started by themselves cannot launch subactors

Create issue
Issue #9 new
James Powell repo owner created an issue

ActorNR, started by itself (from the Run button) cannot launch a subactor. Happens when using a non-strict VI ref to access "Dynamic Launch". I think running the non-reentrant causes "Dynamic Launch" to break, as it theoretically can call ActorNR as a subVI. Using a strict VI ref causes "Dynamic Launch" to instead be reserved for execution.

Comments (6)

  1. James Powell reporter

    Idea: separate from Rather than have parent call, have it message "Launch Actor" and have "Launch Actor" call an independent "Dynamic Launch".

  2. James Powell reporter

    Have reworked the ActorNR launch to use a separate "Dynamic Launch Shell". This reduces the problem significantly.

  3. Log in to comment