QMH Message Management

[FabiolaDelaCueva]

---

@drjdpowell wrote:

---

@Blokk wrote:

About the naming of the "User Events", I totally agree 🙂 Very misleading name, the "Custom Events" just would make more sense 🙂

---

To the C++ programs who wrote the Event system, we're the "Users", hence the name.

---

I digress: This is one of my pet peeves, I would love for the C++ programmers at NI LabVIEW R&D to think of some of their LabVIEW Users as developers and not as users, and yes, this explains the name chosen... that doesn't make it the right name though 😉  Custom events, dynamic events would have been better names, but they were introduced long long long ago, too late to change the name.

[FabiolaDelaCueva]

---

Blokk wrote:

I join for asking about the DQMH "getting started" 🙂

---

BTW, the DQMH also ships with a shipping example that shows a temperature chamber (singleton DQMH module) and Units Under Test (cloneable DQMH modules). It even shows integration with TestStand. 

There is a video showing that example, called "TestStand DQMH Examples" and it is part of the DQMH videos playlist: http://bit.ly/DelacorQMH

[Blokk]

Thanks Fabiola for the many useful info!

[styrum]

Here is a little "food for thought" for all the fans of using user events (and the event structure itself, of course) and corresponding frameworks for communication between parallel running pieces of LabVIEW code (loops, "modules", "actors", "active objects"):

https://forums.ni.com/t5/LabVIEW/Eleven-Ways-to-Update-an-Indicator-from-within-a-subVI-Their/td-p/3...