Call Explain Error Dialogue programmatically in EXE-File

[C.D.]

Hello,

in a built EXE (LabVIEW-Version 2016) I want to call the Explain Error Dialogue programmatically.

In LabVIEW development environment it is reached via menue item "Help->Explain Error...". Programmatically call can reached via invoke node (see picture in attachment). But invoke node doesn't works in built EXE, because the menue item "Help->Explain Error..." does not exist here.

Is there another way to call Explain Error Dialogue?

Thank you in advance.

[GerdW]

Hi CD,

what about the GeneralErrorHandler? It will explain an error too…

[C.D.]

Hi GerdW,

my EXE application gets the error code from an independent slave application (enclosed in a frame of a proprietary TCP communication protocol). The plain text of the frame will update in a string element of my EXE application (see picture in attachment). In case of error the frame contains a error code, which corresponds with the caused LabVIEW error code of the slave application (in the pictured example the LabVIEW error code 63).

For quickly look-up explanation of this error code I will call the Explain Error Dialogue via user-specific context menu of the string element.

Best regards

Christian Dietz

[GerdW]

Hi CD,

this way you get the same error description in a dialog window:

Set the error state, code (and string, if needed) in an eror cluster and call the GeneralErrorHandler to display the Error description…

For quickly look-up explanation of this error code I will call the Explain Error Dialogue via user-specific context menu of the string element.

You can use an event structure to handle that user action and to call the error handler…

[C.D.]

Hi GerdW,

thank you for response, but a fix coded solution is impossible. The parameter of ERROR telegram can contain a LabVIEW error code or sometimes other information. The User must identify type of parameter in individual cases.

A further restriction: Pop up Explain Error Dialogue must not interrupt the EXE application. It should run as a independent window without blocking the calling application.

Best regards

Christian Dietz

[GerdW]

Hi CD,

but a fix coded solution is impossible. The parameter of ERROR telegram can contain a LabVIEW error code or sometimes other information.

No one said you have to use a "fix coded solution". You can create algorithms to handle both types of information.

The User must identify type of parameter in individual cases.

So your algorithm needs to react on user decisions…

A further restriction: Pop up Explain Error Dialogue must not interrupt the EXE application. It should run as a independent window without blocking the calling application.

You can program this in LabVIEW…

Remark: Don't use the OneButtonDialog as it will block your app. Create your own dialog subVI instead.

Conclusion:

- You cannot use that invoke node in an executable, so you need to find a "work-around" to handle your problem.

- I have shown one possible work-around, but you may extend that suggestion to handle your specific requirements.