Modules Event registration when developing

[Walker34]

Hello

That is not directly a DQMH question, but that case is a common issue when using broadcasts. How manage Event Registration when event-clusters are modified? For example, I'm coding my application. I add a new broadcast event in the first module. Then the event cluster of first module is modified. And then, the whole event registration is reordered and I have to modify all my events in the events loop. That's a bit annoying.

It is probably a general case with Labview I think. How do you manage that? Is there a possibility that Labview "recognizes events by names" and adapt events in events loop?

Labview 2024

[Darren]

A best practice for DQMH is to make sure that a module's own Request events is always the first cluster wired to Register For Events. Then dependent modules should be wired after that, then front panel/dynamic events wired after those. And any time you want to add something new, always add it at the bottom and leave the existing order unchanged.

If you wire your Register For Events functions like this, you'll be less likely to see event structure order get messed up when adding new terminals.