I want my module to undergo a sequence of uninterrupted initialisation steps. I understand that if I'm referring to a child module I can get the parent to send an array of messages to instruct this (would this be the way?) But if I want my parent module to init across multiple steps, and so there's no calling code to send the instructions, I'm not clear on how to avoid self enqueuing. Firstly, to start the init at all- I've seen that it's not recommended to put any specific init work into the initialise case, instead using a 'configure' case, but how do I trigger this configure case? I want to just enqueue it from the init case, but is there a better way? Shall I enqueue it in the modules startup code like the initialise is? Then, I need more than one configure step, the first reads the various config files, the second sets up the hardware. Previously i would have self enqueued these, but is there a better way? Should the configure case include a state machine that goes through each of the steps I need? Separate question but loosely related, is it acceptable to put certain initialise code before the module? Like 'pre launch init' in the actor framework. Sorry this is quite a lot, this is my first DQMH project and I'm trying to establish good habits for going forward

DQMH Consortium Toolkits Discussions

How to enqueue initialisation steps without self-enqueuing

No harm done, Dhakkan! I specifically appreciate you pointing out the lack of context in our coding conventions. I went and started tidying the page 🙂

DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )