11-07-2007 05:46 AM
11-07-2007 05:52 AM
Correct me for thinking too simply, but why not just pipe a message back to the parent to do the termination?
Ian.
11-07-2007 06:46 AM
11-07-2007 07:03 AM
11-07-2007 07:19 AM
Yes, that is a good solution, thanks. I am still curious though if it is possible to pass a dialogue handle to a thread function and use it to manipulate the dialogue - like you can in VC++.
Regards,
Marc.
11-07-2007 09:18 AM
I've found another solution. QuitUserInterface() cannot be called from inside a child thread, therefore I created a new CVI callback function DeferredQuit(), which calls QuitUserInterface() instead. I then use PostDeferredCall() to call DeferredQuit() from inside my thread. This ensures that the QuitUserInterface() gets executed as part of the main thread.