Did those example programs linked above help (are you working in LabVIEW 2009)? You can also use LabVIEW to call a DLL, would you consider calling your DLL in LabVIEW?
I'd like to get a little more background information from you. What kind of messages do you need to post back to windows? What version of LabVIEW are you working in? Windows version? 64 or 32 bit?
Thanks for your response.
I am using LabVIEW 8.5. I am pretty sure that the Microsoft Visual C++ DLL source has not been
updated on the NI Developer Zone. I was unable to get it to compile. I was thinking that I might
extend it to allow message posting as well. I am pretty sure that I am going to use a different
The provider of the3rd party app sent me a zip file with a Delphi example. It turns out that the
zip file also contained a .NET 1.1 example as well. I have that example doing what I need to do
from within LabVIEW. Basically, I need to listen for specific messages (WM_CIRRIS_APP0 through
WM_CIRRIS_APP19) and to broadcast messages for the 3rd party app to receive.
I created a .NET 2.0 custom control (WndProc() lives as a protected method of a control) that I
instantiated in LabVIEW. The custom control received no messages.
If I cannot solve the issue any other way, I will write a .NET application that sits between LabVIEW
and the 3rd party app. I will use something (probably sockets) to communicate between
LabVIEW the .NET application. I will, obviously, use Windows messaging to communicate
between the .NET application and the 3rd party app.
Thanks again for all the responses to my question,
Hamilton Woods, Certified LabVIEW weanie
One correction - replace
"I have that example doing what I need to do from within LabVIEW"
"I have that example doing what I need to do. Now I need to figure
out how to do that from with LabVIEW"
Thanks again, and have a blessed day,
I think you are making this more complicated than it needs to be. Muks was pointing you in the right direction... My LabVIEW app uses a USB security dongle that posts messages when it is plugged in or removed. The app has to receive these messages to decide whether to run or not. I used the same files Muks pointed at - it really is pretty straightforward.
I'm not allowed to send out my VIs, but take a look at these screenshots. All you have to do is create the message queue, and then pass the hwnd and queue around as needed.
This newsgroups is not frequently used.
Where do you think you are?
This IS the National Instruments discussion forum linked to by the web address you gave.