Pb with events

[X.]

I did not have any pretention to universal knowledge...

My suggestion (not developed at all in my previous answer) was to adopt a queue-based producer to consumers communication approach. This is nothing new and I found it described differently in many places. Queues are im my opinion (of a newly converted user) very handy for that purpose.

Your Main VI has two while loops. One that contains an Event Structure. One that waits for a local queue signals (I call it the "Action" loop). The event structure loop sends "instructions" (essentially mirroring the events) via a queue to the Action loop, which does respond to the events AND if you need to, sends tasks to parallel VIs (via other queues, which I'd call "Consumer Queues' - of course if you have several Parallel VIs interested in a Main VI event, you may want to replace this queue scheme with a Dynamic Event one).

You Parallel subVIs do not "poll" the main VI. They simply contain a while loop that waits for a new queue element (or dynamic event).

I hope this clarify what I had in mind.

As a side note, I find the big bundle of references in Ben's snapshot quite...big (I'm gonna stay PC here 🙂 If you decide to totally remodel your FP, this is going to break down AND you will have to update all the Parallel VIs that rely on the previous layout...

But again, if things work for you as is, then great!

My 2 cts,

X.

[Ben]

---

@xavier wrote:

I did not have any pretention to universal knowledge...

...

---

Nor do I and if I implied as much with the comment about waiting for others to catch-up" please forgive me.

I am only offering what little I can in the hopes it will help others or encorage further discusion.

LV Architecture is an area where there a precious few examples that show us how to develop large applications. If anyone has images that help in this area please share them so we can all learn.

Just another student of wire,

Ben

[X.]

I forgot to add that I found the "vertical" 3-way connector thingy on Ben's diagram quite lovely. I think what is missing in his diagram are animated gif icons (I could see the rocket launcher animation adding a lot to... the comics book quality of the diagram)

And BTW, I was not using sarcasm in the "knowledge" sentence... at most self-depreciating irony...

X.

[Ben]

---

@xavier wrote:

I forgot to add that I found the "vertical" 3-way connector thingy on Ben's diagram quite lovely. I think what is missing in his diagram are animated gif icons (I could see the rocket launcher animation adding a lot to... the comics book quality of the diagram)

And BTW, I was not using sarcasm in the "knowledge" sentence... at most self-depreciating irony...

X.

---

I'll guess you are talking about the Error Fork Stacker or my modified version that I call an "Up-Stacker".

The Error Fork Stacker was originally written by Mike Porter and can be found in this thread.

Since that code is public, in theory we could ALL have lovely diagrams.

Xavier,

I try to stay on the positive side of things so I appreciate you using those nice words. If you and I ever meet-up at NI-Week, remind me I owe you a beer*.

Ben

* At the current rate I guess I'll have to sponsor the bar tab for the LAVA BBQ.

[X.]

One kudo for that VB*

X.

*virtual beer