Leaderboard

On a related note, when making architecture framework code that includes User/Dynamic events..... A little known fact is that you can register multiple Event Registration Refnums to an individual Event structure. So you ask, "What does this mean to us and why do we care?" First this is what it looks like What is happening here does not show the full power or reason I bring it up. But rather it shows the base Mechanics. This little piece of code registers a different Event Registration Reference for a user event that just got fired.... With a little creativity, you could to a TON of things with that idea (but it's still not why I bring this up. The reason that this technique is so important to event based architectures is that dynamic events do not all need to be lumped together within 1 DynEvent Registration Reference. You can Separate them better based upon functionality. In particular, if you make an architecture that you want someone else to take advantage of, you can isolate your architecture/framework events and registrations and other functionalities within your own framework code and not need to have them modify or tweak their own RegEventRef just because you may have changed or added something to the framework. A great example of this is the ever elusive "Initialization Event" So many people have skinned this cat, it's starting to chafe some. This is a typical way to have an event case fired at startup. But it makes this portion of code a bit bloated and it's just not as elegant as it could be. Now the mechanics of this flow still need to happen. But watch what we can do if we take advantage of the previous technique. The top VI now is a framework level VI that I can drop in any VI that I want to run an INIT case on, without disturbing the definition of the Event Registration Refnum of the rest of the program. The bottom VI just did the same thing by taking that registration process and made it an individual VI that prevents the end user from needing to wire up a bunch of stuff they should not need to worry about. Hopefully this technique (which you can do in 8.6) will aid your architecture