DQMH Event Registrations

[FireFist-Redhawk]

Hey folks,

I'm doing my first pass at something "real" with DQMH, and I'm having difficulty understanding how the events of newly-spawned modules get propagated out to the currently-running modules. I'm using this article as a walkthrough. I spawn the Controller module then GUI module automatically on app startup, but the Controller needs the GUI module's newly-created events to be able to respond to the Exit button.

So do I sent a request to the Controller module to update its registrations for GUI module? Should I just initialize everything, then from the main VI tell every module to update their registrations?

Full project zip attached. My current goal in terms of understanding this is to make the Exit button (in GUI main) fire the Application Closed event; Controller VI 'hears' that and fires the Shutdown event which the Main VI 'hears' and shuts everything down.

[FireFist-Redhawk]

After some monkeying around then some Googling, I found https://delacor.com/dqmh-documentation/dqmh-best-practices/ and it explains this exact thing. Got me on the right path pretty quickly. Documentation for the win!