Nice. I personally like to create a gvl Map that stores user event references as a value with the name of the loop as a key. Each while loop will have its own user event. This eliminates the cluttered reference wire at the front and make the ui look seemless. If I want to send a message I simply type LoopName.Message + wire the variant payload on the sender VI. The sender VI will parse the string, look for the event refere to the loop in the gvl map and generate an event for it. I also invert the event driven state machine by putting the case structure inside the custom user event, event case. There are 0 wires between loops.
Hey Chud. The code in this presentation was just meant as a first introduction. Certainly in production grade code things should be packaged up more neatly. In general my messages are strickly typed as I think this is a powerful developer aid, so I never expose the variant.
thanks, I learned a lot from this video.
Nice. I personally like to create a gvl Map that stores user event references as a value with the name of the loop as a key. Each while loop will have its own user event. This eliminates the cluttered reference wire at the front and make the ui look seemless.
If I want to send a message I simply type LoopName.Message + wire the variant payload on the sender VI. The sender VI will parse the string, look for the event refere to the loop in the gvl map and generate an event for it.
I also invert the event driven state machine by putting the case structure inside the custom user event, event case.
There are 0 wires between loops.
Hey Chud. The code in this presentation was just meant as a first introduction. Certainly in production grade code things should be packaged up more neatly. In general my messages are strickly typed as I think this is a powerful developer aid, so I never expose the variant.