LabVIEW
Using same sub vi code in different data spaces of a project
Solved!
@altenbach wrote:
@billko wrote:
@altenbach wrote:
Yes, of course. That was implied. 🙂
(When I learned LabVIEW, shared clones did not even exist...)
When you learned LabVIEW, Event Structures didn't even exist. 😄
... and there was no UNDO! (Motto: think twice, wire once!) 😄
There was an undo...
Search LabVIEW like a graph! If you really, really want to have a VI that acts as a buffer with multiple instances of that buffer, you can do that.
Explicitly open a VI reference (with Open VI Reference) to the buffer that is reentrant. Each Run VI or Call By Reference (Call And Forget, Call And Collect) will invoke the same clone.
This would give you multiple instances of a FGV...
You might as well put the data in a DVR and use that data in a plain VI, optionally reentrant. That would give you the same functionality, but it will be easier. You'd also be able to make multiple VIs that use the DVR. I'd put the DVR in a class, to keep the VIs organized...
I'd always try to work by wire though.
(EDIT: Sigh. Everything that tst mentioned)
@pushkin wrote:
On your image:
- That buffer only has inputs: how do you get data out of your buffer?
- Ever thought about using clusters to bundle related items (and to minimize connector pane usage)?
Sorry, it's a work in progress. The non-clustering I though would be quicker. I am looking for speed.
Speed to get it working? Or speed of execution?
The first is where to start.
Do you know up front a simple solution is too slow?
Do you know up front a fancy solution is faster?
