drjdpowell's post in Shared Clone Behavior was marked as the answer
In the later LabVIEW versions, one can open the original copy and select View>>Browse Relationships>>Reentrant Items, and that allows one to open the shared clones.
In older LabVIEW Versions, one can (temporarily) set the VI to "show front panel when calledâ€.
However, if your building a message-based architecture, you can just build in a â€œshow front panelâ€ message to your actors/processes/modules/whatever.
drjdpowell's post in Multi Thread Processors - Queue Based (CAL Prep) was marked as the answer
The lifetime of references like Queues are tied to their calling â€œhierarchyâ€ (basically the top level VI). Your main thread creates the Queues, so they die with it. Your other â€˜threadsâ€™, started by ACBR, are actually independent hierarchies. If your main thread finishes before they have a chance to read the final message, then that message is lost.
Normally, I have the receiver of a Queue be the one to create it (and thus own it). Use a temporary Queue to pass the created Queue back to the caller.
drjdpowell's post in Implicit vs. Explicit Property Node: Performance Difference? was marked as the answer
No. Those are static references that donâ€™t need to be closed (closing them does nothing, so donâ€™t bother closing them). You can tell if a reference is static by probing it to see if it changes on each call (if it doesnâ€™t, itâ€™s static).
drjdpowell's post in Preserving run-time class with cluster of objects was marked as the answer
Iâ€™m afraid the "terminal thrallingâ€ (as NI calls it) only works on LVOOP objects directly. Not even arrays of objects, which is what I would particularly like.
BTW, â€œPreserve Run-Time Type" is usually not necessary, as the compiler can trace the object identity through the subVI. Only if the output type could change, do you consider forcing it not to with â€œPreserve Run-Time Typeâ€.
drjdpowell's post in Subpanels not beig displayed was marked as the answer
You only have one subpanel, and a subpanel only holds one VI at a time (dropping the previous VI if you insert a new one). You also seem to be only creating one copy of your subVI (but you opened four separate references to it). If you want four copies (“clones”) of your SubVI, you need to use option 0x8 (Reentrant run) in the Open Reference, and you need four subpanels.
drjdpowell's post in What influence how long it takes to launch an actor? was marked as the answer
Which version of “Launch Actor” are you using? The newer version shouldn’t be closing the reference to “Actor.vi” at all (link).