Too Intrusive Empty Argument Window?

[bienieck]

I'm not sure if DQMH has a dedicated method for reporting potential issues, so I'm sharing my observation here.

I've noticed that when I create a Request event without arguments, an "Empty Argument Window" message always appears, indicating that a dummy boolean will be created. However, it seems that, in practice, only the Broadcast event receives this dummy value.

Is my observation correct, or did I overlook something?

[Darren]

All events with empty arguments window get the dummy parameter. Here it is for a Request I just created:

It doesn't get put on the connector pane of the Request VI, that's probably why you didn't see it.

Also, you can select the 'Don't show this message again' checkbox if you don't want to see the prompt every time.

[bienieck]

Can you check for Round Trip also?

[Darren · Accepted solution]

Oh, I see. Yeah, a Request and Wait for Reply (and by association, a Round Trip) will pop up that dialog, but it won't script any dummy arguments, since the Wait Notifier and Reply Error are already included in the arguments. The reason that Request and Broadcast get the dummy argument is because the arguments cluster must have at least one thing in it.

I feel like the whole point of that dialog is to remind you to add arguments if you forgot. So the purpose of the dialog is still valid, even if the wording isn't exactly correct for Request and Wait for Reply/Round Trip.

I'll file an Issue to the DQMH Consortium about rewording the dialog in that scenario. Should be a very easy fix.