Purpose of status string in MHL data cluster?

[ConnerP]

Greetings, I am trying out the DQMH for the first time and have a minor question. Skip below for the question, as I would like to introduce myself to the DQMH team as a new user. I have been using LV for 4 years now and the JDPowell's Messenger Library for about 3 and have been largely happy with it. Recently I simply had the itch recently to learn something new and landed on DQMH for 2 reasons: 1) No routing addresses everywhere like in Messenger Library and 2) The comprehensive scripting and pre-defined module structure. It has generally been a pleasant experience.

The question is: is there an intended purpose for the "Status" string that is present by default in the Module Data cluster in the message handling loop? I only see it written to once in the UI module in the CML example and never read. I don't see it mentioned anywhere in the documentation. Of course there exists the status broadcast and I would think any module sending a request to poll the status would already be subscribed to the broadcast, making it somewhat redundant. These facts lead me to believe that it was primarily intended as a placeholder. Could someone from the development team either confirm this or elaborate on the intended usage? Thank you!

[joerg.hampel]

Hey ConnerP, great to hear that DQMH seems a good fit for your work. Thank you for giving it a try, and please keep the feedback coming!

As for the Status string in the data cluster, we (my company and our  customers) see it as a placeholder, too, and usually remove it. 

I‘m quite sure that other people might use it differently, I hope they chime in here. That’s one of the great things about DQMH - create your templates as you see fit and make it your own!

[ChrisFarmerWIS]

We have used it in some modules where we wanted to manage an activity log of everything the module was doing.

We would write to the Status field in every MHL case, and then to the right of the MHL CASE structure, record the status to an activity log file.

[doyles]

I have used it as an action logger as well.  I found it particularly useful for debugging a cloneable module that had 60 instances running asynchronously.  I typically ignore it outside of that type of use case.