Sorry for the long title .
If I create a Request and wait for reply Event, in the Public API the Error Cluster from the release notifier VI doesn't get wired to the other error clusters. Please see picture and VI in the attachments.
If an error comes in the Request and wait for reply VI, the notifier does not get created, the release notifier tries to release an empty reference and throws an error. So LabVIEW starts to throw some pop-up windows, cause the error is not wired/handled. Is this a Bug in my DQMH software or is this a feature I did not see?
I am running the newest 4.2.1 Version of DQMH.
Solved! Go to Solution.
if you disable automatic error handling dialogs in LabVIEW options, this dialog will disappear:
This my default settings since ages. If i need a dialog to show a user something happened, i do this explicitly on my own.
If I understand correctly the OP's question, there is a discussion of this problem here. Personally, I like to have automatic error handling turned on, but that's just me.
The next release of DQMH will have the error out wired for that notifier and we will ensure that anything that is scripted has Automatic Error Handling off.
More on Automatic Error Handling:
Brainless LabVIEW is a good source, the slides are at http://bit.ly/brainlesslabview
Thanks for your replies,
I didn´t know, that the AEH plays such an important role while working with LabVIEW. Thanks for the resources about the topic, now the unwired error makes sense to me.
For every one, who has to "repair" their code and turn the AEH off here is a quicksolution for this:
Download the file, put it in the following folder ./<user>/Documents/LabVIEW Data/VI Analyzer Tests, restart LV, create a LV Analyzer Test, select the desired VIs and only check the user defined test, run test, done.
Edit: Here is another source from Darren