Could you have your DLL set a flag on an error condition? If so, your
Labview code could check the flag as often as you like, perhaps in a
parallel While loop.
On Mon, 3 Jan #000 16:39:49 -0800, "Bruce Kingsley"
wrote:
>Ken:
>
>Thanks for the response.
>
>The problem is more complex. The DLL is shared by more than just LabView
>which makes the DLL aware of events that that LabView may not see; example:
>
>LabView maybe performing file I/O or running a panel, but not calling my
>DLL, so there is no error code to return. Since the DLL is always watching
>things, it may detect an event that requires LabView to stop.
>
>
>Bruce Kingsley
>brucek@wolfenet.com
>
>
>
>Kevin B. Kent wrote in message <3870FD6D.2E8B1AFD@usa.alcatel.com>...
>>Br
uce Kingsley wrote:
>>
>>> I've written a DLL that LabView calls for many different functions.
>>>
>>> In case of a major problem, I would like my DLL to be able to tell
>LabView
>>> to stop execution of the program. Is there a hook of some type in LabView
>>> that can do this or a window message I can post to LabView?
>>>
>>> Bruce Kingsley
>>> brucek@wolfenet.com
>>
>>I would hope that you are returning error codes from your DLL calls.
>>If this is true then you can use that code along with either the
>>Error Handler, or possibly the LV built in "STOP" , "ABORT"
>>functions.
>>
>>Kevin Kent
>>
>
>